(#103) Adds an option to produce MSIs after the Chocolatey Package

[JPRuskin]

Description Of Changes

• Adds a new option to produce the MSI after the Chocolatey package
  • This new option, MsiUsedWithinNukpg, defaults to the current behaviour (true)
  • Naming is hard, and I'm happy to reverse the logic and rename this
  • When set to false, dependencies for the MSI steps are modified such that it is produced after any Chocolatey packages
• Adds a new tool for WiX, such that projects don't need to embed or handle providing these files separately
  • This actually shouldn't break existing projects that use the MSI functionality (e.g. ChocolateyGUI) as it will load the files to the root tools directory but not change any existing tools - but they should be updated. I have a branch ready for GUI, whenever this CCR update is released and versioned.

Motivation and Context

• We needed to produce an MSI containing a Chocolatey Package

Testing

1. Load the ENGTASKS-2800/msiBuild branch of chocolatey/choco
2. Add these changes to the Chocoatey Cake Recipe in use
3. Run a tagged build (or disable the added requirement for MSIs to build on a tagged build in the recipe.cake file)
4. Find an MSI within code_drop/MSIs (should be identical to previously produced Choco CLI MSIs)

Operating Systems Testing

• Windows 10
• Windows 2019

Change Types Made

• ~[ ] Bug fix (non-breaking change).~
• [x] Feature / Enhancement (non-breaking change).
• ~[ ] Breaking change (fix or feature that could cause existing functionality to change).~
• ~[ ] Documentation changes.~
• ~[ ] PowerShell code changes.~

Change Checklist

• ~[ ] Requires a change to the documentation.~
• ~[ ] Documentation has been updated.~
• ~[ ] Tests to cover my changes, have been added.~
• [ ] All new and existing tests passed?
• ~[ ] PowerShell code changes: PowerShell v2 compatibility checked?~

Related Issue

Fixes #103

[gep13]

@JPRuskin thanks for getting this added!