Merge PrismLauncher:8.0 to unmojang

[evan-goode]

Merge tag '8.0' into unmojang-8.0

Resolves: https://github.com/fn2006/PollyMC/issues/115

Upstream changelog: https://github.com/PrismLauncher/PrismLauncher/releases/tag/8.0

(Imcomplete) list of changes in 8.0 relevant to PollyMC:

• Prism has dropped support for Mojang accounts
  • https://github.com/PrismLauncher/PrismLauncher/pull/1656
  • Added it back to PollyMC primarily since the Mojang authentication code is also used for authlib-injector accounts. Some users may also still want to be able to log in to Mojang accounts for some reason: https://github.com/fn2006/PollyMC/issues/115#issuecomment-1805384658, even if they do not provide authentication to multiplayer servers.
  • To my surprise, I could still log in to a Mojang account, get its skin, and launch the game. Authentication to servers, of course, did not work.
  • Tested: logging into authlib-injector, Mojang, and MSA accounts and launching the game.
• Prism has added a built-in updater for Windows and Linux that I assume provides similar functionality to Sparkle on macOS: https://github.com/PrismLauncher/PrismLauncher/pull/1268. There is a Launcher_UPDATER_GITHUB_REPO variable in CMakeLists.txt that specifies the repo checked by the updater. I have changed this to the PollyMC repository, and since PollyMC follows almost the same CI/release patterns as Prism Launcher, it might work with PollyMC, too, but I have not tested it yet.
• Add macOS support to Nix
  • https://github.com/PrismLauncher/PrismLauncher/pull/1485
  • Untested
• The "PollyMC-Linux-8.0.tar.gz" and similar build artifacts were renamed to "PollyMC-Linux-8.0-Qt5.tar.gz" to match their "PollyMC-Linux-8.0-Qt6.tar.gz" counterparts.
• Removed Windows MSVC Legacy builds
• Removed Quilt Beacon toggle, the beacon is now always disabled: https://github.com/PrismLauncher/PrismLauncher/pull/1547, https://github.com/PrismLauncher/meta/pull/23
• Prism removed FTB support in 7.0, but I tested creating an FTB instance to make sure it still works in 8.0

[evan-goode]

FYI, I didn't know this until I Googled "how to review a merge PR" and found https://haacked.com/archive/2014/02/21/reviewing-merge-commits/, but you can run git diff-tree --cc on this commit and it will show only hunks that changed as part of the conflict resolution, which results in only about an 800 line diff.

[lemonzest79]

Just tried the debug build of this from the github actions and things seem to be working ok after I found the extra info for the api url and stuff as it did not migrate my Ely.by accounts after doing so I could log into my 2fa enabled ely.by accounts (needed to do the usual password:token method as no 2fa input box anymore that was available with 7.2) afterwards I could log into my ely.by enabled servers ok and skins worked.

[evan-goode]

Sorry for the force pushes, I screwed up by merging 8.0 on top of commits from another feature branch, and then re-writing history on the other branch.

Just tried the debug build of this from the github actions and things seem to be working ok after I found the extra info for the api url and stuff as it did not migrate my Ely.by accounts

Thanks for testing. I just filed https://github.com/fn2006/PollyMC/pull/117 to auto-migrate Ely.by accounts to the new format, would you mind seeing whether that works for you (once the CI finishes the build you need)? That branch is based on 7.2 not 8.0 FYI.

Maybe we should add a message to that dialog box about 2FA on Ely.by. Adding the dedicated field back is also doable, but it doesn't make much sense since it's an Ely.by-specific feature. If there's some other auth server that expects 2FA formatted like hunter2-12356 instead of hunter2:123456 then it's not gonna work.

[evan-goode]

The updater seems to work on the AppImage, at least to report that there are no updates, but of course I couldn't test the actual updating.

[evan-goode]

Test Nix build on macOS, works great. Going to mark this no longer a draft since it's closer to mergeable.