feat(installer/windows): add wix installer

[ReenigneArcher]

Description

This PR adds a WIX installer for Sunshine. The NSIS installer will be removed at a later point after any bugs with the WIX installer are ironed out.

This is a requirement for having an ARM64 installer for #3905 or #3369

TODO:

• custom actions are not running
• shortcut is not created
• vigembus installer won't run because we're already running an msi installer... proposed solution: feat(windows): add ViGEmBus driver management API and UI integration #4625
• application icon not showing in installed apps screen
• docs for creating installer (need dotnet)
• fix start menu directory structure
• should we hide cmd/powershell windows? refactor(packaging/windows): installer script execution #4675
• document process for migrating from old installer to new one

For first release after this is merged, we will keep both exe and msi, so that the winget automation will still work to auto update winget. We will then to update winget manually to use the msi

• [Question]: How will this action work when adding an architecture? vedantmgoyal9/winget-releaser#322
• https://github.com/microsoft/winget-pkgs/tree/master/manifests/l/LizardByte/Sunshine
• change winget from exe to msi

Screenshot

Issues Fixed or Closed

• Resolves Sunshine: change windows installer to WiX roadmap#76

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 15.14%. Comparing base (22065bf) to head (953c971).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3916      +/-   ##
==========================================
- Coverage   15.17%   15.14%   -0.04%     
==========================================
  Files          95       95              
  Lines       19874    19874              
  Branches     9178     9178              
==========================================
- Hits         3016     3009       -7     
+ Misses      15685    15003     -682     
- Partials     1173     1862     +689     

Flag	Coverage Δ
Archlinux	11.20% <ø> (ø)
FreeBSD-14.3-aarch64	?
FreeBSD-14.3-amd64	13.23% <ø> (-0.01%)	⬇️
Homebrew-ubuntu-22.04	13.43% <ø> (ø)
Linux-AppImage	11.60% <ø> (ø)
Windows-AMD64	13.48% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 42 files with indirect coverage changes

[codecov]

Bundle Report

Bundle size has no change ✅

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cgutman]

The latest NSIS version now runs properly on ARM64 systems, so we can stick with NSIS if we want. WiX does make it easier to support having a single unified installer for both x64 and ARM64 binaries if we want that.

[ReenigneArcher]

Good to know. I still need to setup a VM to test this out.

I think msi would still be nice to use, especially for anyone installing Sunshine with a script as it supports more CLI options. I discovered in a recent change that I couldn't even get the output of the installer scripts to a log file with NSIS.

Do you know the process for unifying the installer? That would be pretty nice.

[ReenigneArcher]

This is basically working now, just need to nail down a few things.

should we hide cmd/powershell windows?

Any preference?

I think I will also have one single script that calls all the other scripts, especially if we're going to have the window show. And then output the stdout out from the script to a log file, as currently I don't think this is logged by the msi installer.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ReenigneArcher]

Should we wpdate getting_started.md installer links?

Provide MSI links only or both EXE and MSI?

PR is draft, review not requested. I already have updating docs on the todo in the PR request body.