fix: Add MSI package for Windows to enable per-machine installs.

[Oliver-Loeffler]

Scene Builder is published for Windows using a per-user installation MSI package, which is created by JPackage.
In certain scenarios, a per-machine install is desired.

Unfortunately, when using JPackage, one has to decide upfront between per-user or per-machine install. Having an option in the installer would require an update to JPackage or to the WXS/WXI files used by JPackage.

As an alternative approach, there could be a new Scene Builder build artifact, a MSI file for per-machine installs. Usually per-machine installs require administrative privileges on Windows whereas per-user installs don't.

The per-machine installer will use Windows default programs folder for installation (C:\Program Files\SceneBuilder) whereas the existing per-user installer will use C:\Users\<UserName>\AppData\Local\SceneBuilder\ instead.

Having 2 artifacts allows administrator to implement those into existing provosioning and deployment processes without additional use of command line flags or switches.

Per-User Installer

Per-Machine Installer

Issue

Fixes #672

Progress

• Change must not contain extraneous whitespace
• License header year is updated, if required
• The PR name must follow the pre-defined format
• Verify the contributor has signed Gluon Individual Contributor License Agreement (CLA)

[abhinayagarwal]

Single Package Authoring has been available for a very long time now. May be we can override WIX configuration to add this.