Implement Submodules for YamlCreate

[Trenly]

In an attempt to break YamlCreate down into easier to manage pieces, I've begun to implement some portions as PowerShell modules. This PR does the following:

• Adds VirtualTerminal sequences as a Module

• Removes the Write-MultiColorLine function and uses the sequences from the VirtualTerminal module instead

• Moves installer type detection to a separate module

• Improves WIX installer detection by checking the file metadata for the program which created the MSI

• Adds a module for keypresses as framework for future menuing improvements

• Adds a parent module which imports all the necessary sub-modules

cc @mdanish-kh @denelon

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[denelon]

I wonder if we're getting closer to the point where we could have some "Microsoft.WinGet.Something" module (potentially leveraging wingetcreate) to make it easier to generate/test manifests. I don't want to block YAMLCreate on wingetcreate, but I know we're going to need/want PowerShell parity for PowerShell users.

[Trenly]

I wonder if we're getting closer to the point where we could have some "Microsoft.WinGet.Something" module (potentially leveraging wingetcreate) to make it easier to generate/test manifests. I don't want to block YAMLCreate on wingetcreate, but I know we're going to need/want PowerShell parity for PowerShell users.

We probably could. If wingetcreate had PowerShell modules, that would be interesting

[denelon]

• Build a PowerShell cmdlet for wingetcreate winget-create#25

I think we'd include the binary in the module for that particular use case.