Upgrade 1.6 schema to 2020-12

[Trenly]

• I have signed the Contributor License Agreement.
• This pull request is related to an issue.
  • Resolves Upgrade to schema draft 2020-12 #3475

This does not upgrade the Settings Schema as it is not reliably versioned

• Support Versioned Settings Schema #2963

and it also does not upgrade the packages schema, as I felt it was not appropriate to create an entirely new schema version just for a base schema upgrade

The reason for changing to defs is based on the semi-incompatibility from draft 2019-09 and for better adherence to the standard.

The old syntax for these keywords is not an error (and the default meta-schema still validates them), so implementations can therefore offer a compatibility mode. However, migrating to the new keywords is straightforward and should be preferred.

---

Microsoft Reviewers: codeflow:open?pullrequest=#3478

[yao-msft]

/azp run

[azure-pipelines]

No commit pushedDate could be found for PR 3478 in repo microsoft/winget-cli

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[denelon]

Does this still work in Visual Studio Code?

I think they only "support" an earlier version of JSON schemas.

[Trenly]

Does this still work in Visual Studio Code?

I think they only "support" an earlier version of JSON schemas.

It seems to work

[denelon]

I don't know if this would have any impact on any of the rest of our validation code or not. I'll let one of the engineers review first.

[denelon]

It looks like we should go with $defs
https://json-schema.org/draft/2019-09/release-notes.html#semi-incompatible-changes

There weren't examples in the 09 schema, but there were a few in the 12 schema under:
https://json-schema.org/draft/2020-12/release-notes.html#open-tuple

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).