Update schema to 1.12 with Font InstallerType

[dkbennett]

• Updates schema to 1.12 and adds type "font" as a valid InstallerType and NestedInstallerType in the schema.
• Adds InstallerType Font to the manifest and associated Enum conversions.
• Updated some of the NestedInstaller validation that had assumed Portable type as the only type that could have multiple installer files (fonts can also have many fonts in a package).
• Added validation for 1.12 fonts in the manifest and associated tests for the schema version.

This PR does not add any functional support for Fonts, only the validation and schema update so the new schema can be used and is valid in the related WinGet tooling.

Tested:

• Passed the AppInstallerCLITests with [ManifestValidation] and ensured a clean result.
• Added new tests for the v 1.12 manifest updated with the new installer types in the test installer manifest to ensure Fonts are correctly passing the validation.

Closes #5686

• I have signed the Contributor License Agreement.
• I have updated the Release Notes.
• This pull request is related to an issue.

---

[JohnMcPMS]

Would it be possible to get two more commits added:

1. Move your current 1.12 schema files out and copy the 1.11 files into the 1.12 directory, otherwise unchanged. Commit this.
2. Move your 1.12 files back in over the 1.11 files. Commit this.

Without at least a baseline of the 1.11 schema files, it is extremely annoying to review the changes between 1.11 and 1.12.

Another option that might set things up for success in the future would be to call the 1.12 directory latest and set the precedent of the pattern being:

1. copy the latest directory to the appropriate previous version name [so next time it would be v1.12.0]
2. update latest with the new changes

If you do this, make sure to create a commit in latest with 1.11 before putting the 1.12 files there.

[Note, 1.11 is actually the stand in for N-1, which I now think was 1.10?]

[dkbennett]

Would it be possible to get two more commits added:

1. Move your current 1.12 schema files out and copy the 1.11 files into the 1.12 directory, otherwise unchanged. Commit this.
2. Move your 1.12 files back in over the 1.11 files. Commit this.

Without at least a baseline of the 1.11 schema files, it is extremely annoying to review the changes between 1.11 and 1.12.

Another option that might set things up for success in the future would be to call the 1.12 directory latest and set the precedent of the pattern being:

1. copy the latest directory to the appropriate previous version name [so next time it would be v1.12.0]
2. update latest with the new changes

If you do this, make sure to create a commit in latest with 1.11 before putting the 1.12 files there.

[Note, 1.11 is actually the stand in for N-1, which I now think was 1.10?]

Fixed this using your future-proofing recommendation:

• Created 'latest' folder for schema.
• Copied 1.10 into latest, renamed version to 'latest' as well in the filename.
• Committed the above.
• Moved 1.12 into latest, renamed file version to be 'latest' for exact file diffing.
• Committed that. The clean diff for easy viewing is now here: e0a1a01
• Updated the resource for 1.12 to point to the latest.