#420: Create Windows Installer with WixToolset

[alfeilex]

Fixes: #420

This PR implements the creation of a MSI file for Windows Installer with WixToolset

It includes:

• The Windows Installer Build Package with UI Sequence:
  • Accept License
  • Continue with default installation (default C:\projects) or customize
    • Volume Drive
    • Root Folder or User Home Folder
  • Copy files into installation folder and run ideasy.exe -f install
• The integration of the WixToolSet build logic into the Nightly Build and Release workflow

[coveralls]

Pull Request Test Coverage Report for Build 13564776342

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.255%

---

Totals
Change from base Build 13563968558:	0.0%
Covered Lines:	7867
Relevant Lines:	11077

---

💛 - Coveralls

[alfeilex]

@alfeilex now that my PR #1055 is merged, your MSI installer only needs to call ideasy.exe -f install:

IDEasy/cli/src/main/package/setup

Line 3 in 4caff46

./bin/ideasy -f install

Is added but has to be tested when #1084 is merged.

[hohwille]

@alfeilex thanks for this PR and finding a solution to this tricky story 👍
I checked the following aspects:

• installation is happening via new approach (ideasy -f install)
• the installation is triggered from the correct directory (workaround for bug Fix CWD for InstallCommandlet #1084)
• uninstallation is happening correctly (ideasy -f uninstall)
• license agreement is implemented nicely with the proper license (via RTF and follow up issue Add Conversion of LICENSE.adoc to RTF Format #1056 was created)
• what I am unsure is if the user can pick the installation location and that will be honored by the installation (I was expecting that IDE_ROOT would be set according to the users choice before ideasy -f install is called)
• all is integrated into nightly build and looks sane to me. However, I do not immediately understand if the native image will be included in the MSI.
• Release download link to MSI was added
• CHANGELOG was adopted

So IMHO this is already in a great state, even though it is not entirely completed.
I would therefore merge it as is and test it with a nightly build, download MSI and test it.
Then we can improve and complete in a follow up PR.