Match WIX logic to wingetcreate

[Trenly]

@OfficialEsco @jedieaston

As I was working on 3.0, I found a way to extract most of the MSI database to an object in PowerShell. This allows for the same logic as microsoft/winget-create#220 and should more reliably detect WIX installers, even if the CreatedBy doesn't match one of our expected values. This PR backports that solution into the 2.0 script

[OfficialEsco]

Does this work with and solve the #151 error?

[Trenly]

Does this work with and solve the #151 error?

It does work with #151 but it doesn't solve the issue of not being able to detect wix vs msi if the file itself does not end in .msi.

There are multiple reasons for that -

1. If a file is not truly a windows installer database (msi or wix), then attempting to read the database results in many, many errors. I haven't yet found a way to reliably prevent these errors other than checking the file extension
2. Powershell and downloading files is weird. Trying to use the method of streaming the content and then saving it using the ContentDisposition header causes issues for several cases with proxies, redirects, user configurations, and all sorts of other things. I believe I have a way around this for v3.0 (still investigating), but there isn't really a way to backport that solution into the 2.0 script without rewriting major sections of the code. This is where (currently) we have to rely on the URLS provided to set the file extension while downloading the file. I do have some work planned to make the detection and matching better, but I don't currently have a way to fix it for most scenarios.
3. There are only two times when detection of installer type is used. One is in the new package (full update) flow. The automatic detection here shouldn't be critical since it prompts for the installer type if it cannot detect it. If the user sets it to MSI or WIX, then Check for productcode even if extension doesn't match #151 should take over and handle the product code. The second time autodetection is used is during the quick upgrade flow, if and only if the installer type is currently msi. This is to try and detect if a package is actually WIX. The automatic detection isn't critical here since if the downloaded file is not an MSI, then the currently set installer type remains and is not updated. At every point the autodetect is used, if the script isn't 100% certain of the installer type it allows for user input or keeps the input the same.

[OfficialEsco]

@jedieaston would you mind taking a look at this 🔥 code?

[jedieaston]

Oh gosh, sorry for the delay. This looks great!