Installer repo should explore using arcade tasks for msi generation

[mmitche]

The installer repo uses a series of powershell scripts for msi generation right now. These then have to be kept in line with the light command package drop creation (if inputs change). They're also generally hard to understand (from a command line standpoint) since they pull in about 20 unnamed parameters. For example:

    <Exec Command="powershell -NoProfile -NoLogo $(SdkGenerateBundlePowershellScript) ^
                      '$(SdkMSIInstallerFile)' ^
                      '$(DownloadsFolder)$(DownloadedAspNetCoreSharedFxWixLibFileName)' ^
                      '$(DownloadsFolder)$(DownloadedSharedFrameworkInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedHostFxrInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedSharedHostInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedWinFormsAndWpfSharedFrameworkInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedNetCoreAppTargetingPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedNetStandardTargetingPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedNetCoreAppHostPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedAlternateNetCoreAppHostPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedArmNetCoreAppHostPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedArm64NetCoreAppHostPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedAspNetTargetingPackInstallerFileName)' ^
                      '$(DownloadsFolder)$(DownloadedWindowsDesktopTargetingPackInstallerFileName)' ^
                      '$(FinalizerExe)' ^
                      '$(LatestTemplateMsiInstallerFile)' ^
                      '$(ManifestsMsiInstallerFile)' ^
                      '$(CombinedFrameworkSdkHostMSIInstallerFile)' ^
                      '$(WixRoot)' ^
                      '$(SdkBrandName)' ^
                      '$(MsiVersion)' ^
                      '$(SDKBundleVersion)' ^
                      '$(Version)' ^
                      '$(MicrosoftWindowsDesktopAppRuntimePackageVersion)' ^
                      '$(CombinedFrameworkSDKHostInstallerUpgradeCode)' ^
                      '$(SdkDependencyKeyName)' ^
                      '$(Architecture)' ^
                      '$(MicrosoftNETCoreAppRuntimePackageVersion)' ^
                      '$(MicrosoftAspNetCoreAppRuntimePackageVersion)' ^
                      '$(CliProductBandVersion)' ^
                      -InformationAction Continue " />

It would be much better to use the built in tasks (and improve them if necessary), for the following reasons:

• Central versioning of the WiX tooling
• Automatic light package generation
• Less custom code.

[michellemcdaniel]

Just to add to this, also to RPM generation.

[MiYanni]

@joeloff Is this a reasonable goal to have? If so, we can transfer this issue to dotnet/sdk.