This also throws away the logic of updating
`API.LocalUser.Value.Statistics`. Components should rely on
`LocalUserStatisticsProvider` instead for proper behaviour and ability
to update on statistics updates.
Because even if you somehow bypass the breakage that bricks your install
by installing the missing libssl-1.0 or whatever
(https://github.com/ppy/osu/issues/30648#issuecomment-2478856055),
there's another brick upstream
(https://github.com/ppy/osu/issues/30648#issuecomment-2478926177,
https://github.com/velopack/velopack/issues/355).
Can we even downgrade like this? No idea. How does one test this? No
idea. At this point I am like a headless chicken, screaming into the
void trying to restore any semblance of order into my crumbling
universe.
If this is tried and linux is still broken with the libssl garbage, then
the `osulazer-2024.1115.1-linux-x64-*.nupkg` assets should be pulled
from the release, which should be enough to stop the game from
auto-updating. Maybe the appimage itself can stay up and people can
upgrade manually if they so desire. Or maybe not. Who knows.
A `false` value marks the user as being on the latest release, and
notifies them as such when clicking the button in settings. In reality,
we don't know whether this is the case yet - we're just deferring the
check.
Somewhat minor change because the chance of a user manually going into
settings and clicking the button is very small.
If a user was to manually check for updates via the button, the recheck
would have been fired. This is a recent regression.
I kinda want to reorganise this code (the button press for check for
udpates shouldn't even get close to the recheck code IMO) but for now
this seems like one we should quickly fix.
Addresses https://github.com/ppy/osu/discussions/29774.