Launcher Overhaul

[xTVaser]

This has an absolute ton of changes. It's not 100% ready yet, but I'm opening it early to start crossing off issues. I don't think this will be done/tested in time for this months release. But probably next month's.

The major change here is that the launcher's release will no longer be tightly coupled to the jak-project's release. Which is to say, it will no longer distribute the relevant binaries as a sidecar. This means the launcher will manage your jak-project release(s) and only has advantages from my perspective:

• allows you to easily rollback to a previous release (ie. we break something)
• allows for custom bundles of gk/goalc/etc -- think mods
• simplifies the dev story (no longer need to have the binaries in the dev path)
• simplifies deployment/release pipelines/etc
• smaller download size
• we can mock the calls to tauri for frontend testing trivially via the provided tooling

The only disadvantage is related to testing (ie. ideally you would test the launcher works with the consumed binary from jak-project _before_releasing) But this is a non-issue -- we can't do any of this testing without an ISO within the CI.

This moves a lot of the typescript code (frontend) into the rust layer (backend). For a few reasons:

• Way better language for ensuring correctness
• The ideal spot to run the processes / extract the releases / etc (lots of crates to do this sort of thing, and do it FAST)
• Way better logging utilities that can pipe to files -- important as we also want to mirror the stdout/stderr of our "sidecars" "in the same way
• I want to get better with rust

Fixed Issues

• Fixes Remove data directory in program files after install.  #102
  • There are reasons why we keep the data directory around (besides file permission issues) but it no longer exists, so easy fix there
• Fixes add release notes to the update prompt #8 Fixes handle the updating prompt ourselves, the default prompt is kinda ugly AND gets covered up by the launcher window #7
  • The new update process needs to be tested, but is much easier in that we don't need to worry about the jak-project release notes as part of the normal release process
• Fixes Check what directory the launcher is installed in, and if its not the default path display a dialog box #51 Fixes Any way to change OpenGOAL-Launcher extraction data folder? #105
  • This should be irrelevant now, the user can pick whatever directory they want. A cross-drive install needs to be tested though because it's still not clear to me why that was a problem before
• Fixes Requires the following requirements #54
  • Wording was changed
• Fixes Possible to have an installation that does not contain goalc at %appdata%\Roaming\OpenGOAL-Launcher\ #74
  • Though the underlying issue here is a little ambiguous
• Fixes custom install path settings #13
  • Main change in this PR
• Fixes Switch from npm to yarn #100
• Fixes [bug fix] launcher does not work offline #32
  • It's worth pointing out that Tauri's installer by default already installs WebView2 if you don't have it. I changed it to add around 2MB to the installer to increase compatibility. But I don't see the need to be fully "offline". Once the user has downloaded the launcher, and fully installed a game -- it is offline. If something breaks (other than the obvious, like checking for updates) that's a separate bug we'll have to address. https://tauri.app/v1/guides/building/windows#webview2-installation-options
• Fixes Better error UX story when doing decompile or compile #11
  • Uses the same UX as a normal installation
• Fixes A button that restores settings to their default state for the specific game. #9
  • Feature added, renames the current one to pc-settings.old.gc
• Fixes No UI indicator during sync process #17
  • Uses the same UX as a normal installation now as well
• Fixes Detect Vulkan support #4
  • I pulled in wgpu in order to get GPU information and this seems to easily allow VK checks as well.
    • Though if this doesn't work out, I think the actual place to handle this is in the C++ project, since that actually has the GPU libraries and logic. Could add a test CLI arg or something to report if the user supports it.
• Fixes Enhanced log display system #16
  • This PR will improve the log output substantially, and also there is a feature where the user can download a single zip file with everything someone helping on support could need.
• Fixes Throw nice understandable error if provided unexpected junk. #15
  • This boils down to "error handle well" which is the last thing that needs to be done in this PR along with testing

Deferred

• Launcher only supports ISO files #3
  • The extractor itself is broken for this, unless you run the entire gamut at once with a folder path, it assumes the data will be in data/iso_data which when you are explicitly providing the folder -- is wrong. I also need to check if it validates the folder contents
• Properly support launching a REPL on linux #85
  • This doesn't seem to be an issue on windows, but I've disabled REPL launching on linux for now anyway. The reason is that we need to properly handle the fact that a linux user could have a multitude of different terminal programs installed -- each with their own different set of flags to work properly. The nice approach seems to be to just defer this burden to the user, let them pick the program they want to use / and specify the flags in the settings menu. But this is something for a later date.
• Background videos don't play on linux or macOS if using webm format #107 - new issue, linux and gstreamer doesn't seem to like webm files. Test with mp4