Improve Installer Type Detection for YamlCreate

[Trenly]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

This PR improves the installer type detection in YamlCreate by relying on the actual binary of the file instead of just the file extension.

cc @mdanish-kh @denelon

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[denelon]

Does this require any changes to component governance, or are these just "new"/"recent" versions of libraries being pulled in?

[Trenly]

Does this require any changes to component governance, or are these just "new"/"recent" versions of libraries being pulled in?

@denelon - powershell-yaml is just a new version; The other two - MSI and NTObjectManager are new and will likely require component governance review.

[Trenly]

Licenses

Component	License	Link
powershell-yaml	MIT	https://github.com/cloudbase/powershell-yaml/blob/v0.4.12/LICENSE
MSI	MIT	https://github.com/heaths/psmsi/blob/3.3.4/LICENSE.txt
NTObjectManager	Apache-2.0	https://github.com/googleprojectzero/sandbox-attacksurface-analysis-tools/blob/v2.0.0/LICENSE.txt

[mdanish-kh]

1. Test-Inno not working would be the only blocking comment

2. nit: For consistency since you used the hexadecimal notation in Test-IsFont, we may either want to modify all decimal notations where we use byte[] to follow hexa, or change the hexa to be decimal notation in Test-IsFont. I'm partial towards the hexadecimal style as it's easier to read and matches with the tools one may use to inspect these files