This always confuses me since stable used this for the main storage
location of the icon. We don't reference this anywhere so it's just
weird to still keep this around.
Of note, this has a lazer icon from many years ago still inside it.
I'm not entirely sure how this works, but CI was testing against the
updated Velopack package, whereas my local package was outdated and had
4 args.
Previous commit merges master to update the package version, this commit
fixes the args.
If we're the only app for a filetype, windows will automatically associate us.
And if a new app is installed, it'll prompt the user to choose a default.
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.