Add light/lit command packages

[mmitche]

This adds light command package generation to aspnetcore.
After build of a wix project, generate a light package based off of the inputs that are sent to light.exe/lit.exe.

[dougbu]

At a high level, why is this change needed❔ We already produce *.msi installers e.g. https://github.com/dotnet/aspnetcore/blob/release/5.0/src/Installers/Windows/Wix.props#L10-L15 and the MSIs in BlobArtifacts in (last release/5.0 build) https://dev.azure.com/dnceng/internal/_build/results?buildId=789717&view=artifacts&type=publishedArtifacts

[mmitche]

At a high level, why is this change needed❔ We already produce *.msi installers e.g. https://github.com/dotnet/aspnetcore/blob/release/5.0/src/Installers/Windows/Wix.props#L10-L15 and the MSIs in BlobArtifacts in (last release/5.0 build) https://dev.azure.com/dnceng/internal/_build/results?buildId=789717&view=artifacts&type=publishedArtifacts

This is so these installers can have files replaced and re-linked after having those files signed. You can decompile msis, exes, etc. to do this operation, but it is very hard because database needs to be altered heavily after the files are signed (e.g. the length of files change). This change effectively just captures the pre-link artifacts (files mentioned in the wixobj's) and creates a little file drop and command line script that can be used the create the MSI. Then it becomes trivial to sign the input files and run the script to produce a signed msi.

[dougbu]

We sign the input files in a separate step from one one that builds the *.wixproj projects. But, this is about enabling the whole signing (Chrome was kind and auto-corrected that to "singing", must know this is probably good news 🎆) process to be moved out of our pipeline, right❔

[mmitche]

We sign the input files in a separate step from one one that builds the *.wixproj projects. But, this is about enabling the whole signing (Chrome was kind and auto-corrected that to "singing", must know this is probably good news 🎆) process to be moved out of our pipeline, right❔

Yep. This effectively creates a way to recreate the msis/exes/bundles/wixlib's out of the context of the build.

[mmitche]

@dougbu Depends on #25373

[dougbu]

So this will fail until #25373 goes in❔ Changes on top of that look fine though please remember to align the Microsoft.DotNet.Build.Tasks.Installers version and SHA when resolving conflicts with that PR (or whatever the final commit is if the current build fails).

[mmitche]

So this will fail until #25373 goes in❔ Changes on top of that look fine though please remember to align the Microsoft.DotNet.Build.Tasks.Installers version and SHA when resolving conflicts with that PR (or whatever the final commit is if the current build fails).

Yep and will do.