Support for 1.2 Schema Additions

[ryfu-msft]

This PR updates the 1.2 schema to incorporate the proposed changes from #1891. This only adds functionality for parsing and processing the new schema additions and does not include their respective feature support.

Also includes additional proposed arguments and settings schema changes for installing portables. Excludes some of the installer manifest changes for the portable feature as those will be included with the work for the portable install feature which will have more thorough testing.

Related to:

• Relax Regex Validation on Protocols #1994
• Manifest Field for User Manual / Documentation #1984
• Increase FileExtensions limit to 512 #1916
• Add an optional URL to Expected Return Codes #1889
• Add a "custom" Expected Return Code #1888
• Add Purchase URL to schema #1345
• Add the ability to identify unsupported arguments #1277
• Add a notes/info field to manifests. #607
• [New Feature]: Add ability to display warning to user before upgrade #1786

Microsoft Reviewers: Open in CodeFlow

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Trenly]

Sorry for not leaving some of these comments regarding number of nodes and the enum in the original PR (#1996)

[Trenly]

Looking at the documentations a bit more, it seems that with the proposed schema, the Documentations (if not null) could be an empty array, or an array of empty objects.

I also think that we should force quality here, and require that each Documentation require the URL and Description, as a documentation without a URL is meaningless and a URL without a description may be confusing

[ryfu-msft]

Looking at the documentations a bit more, it seems that with the proposed schema, the Documentations (if not null) could be an empty array, or an array of empty objects.

I also think that we should force quality here, and require that each Documentation require the URL and Description, as a documentation without a URL is meaningless and a URL without a description may be confusing

I discussed with the team and I decided to not follow through with these changes. There are a lot of components such as WingetCreate, WingetSvc, and other 3rd parties that rely on the schema and adding more constraints could be breaking. These changes will require more thorough testing that I won't address in this PR, so I will stick with the existing pattern.

[yao-msft]