For package-managed solutions that set `OSU_EXTERNAL_UPDATE_STREAM`
(which overrides the config value), we should not allow the user to
change the release stream themselves.
There are two primary paths here:
1. A user requests an update. The existing request is used if it's in
progress, or a new request is made and processed immediately.
2. Something is changed (e.g. the release stream) that triggers a
background request. A new request is made to run after the existing one.
I am aware there are more throughout the codebase but intentionally left
the remaining mentioned for one reason or another. The intention here is
to mainly change user-facing versioning to change the positioning of the
"lazer" term (to be where we would expect "cuttingedge" or "beta" to
be).