Add support for JSON serialization

[mdanish-kh]

• Have you signed the Contributor License Agreement?
• Are you working against an Issue?
  • Resolves Support creating manifests as JSON #456

Changes

• Add a new CLI arg --format to specify output manifest format (json, yaml etc).
• Added a new user setting to specify the manifest format (inline --format arg takes precedence over this value)
• Refactored current Serialization.cs for future extension of other serializations
• Added check to only allow YAML submissions to community repository
• Implemented support for deserialization from local files / GitHub repo contents of JSON format. Refactored GitHub flow to allow submission of json manifests.

Validations

Added E2E tests for JSON, and added a bunch of unit tests.

Important

The tests will only pass once changes in microsoft/winget-pkgs-submission-test#4784 are merged since I had to refactor the directory structures as well. For local testing, you can pull the changes in that PR to the master branch of your fork and run the tests locally;

cc @denelon @Trenly from the original issue for any naming/design considerations

---

Microsoft Reviewers: Open in CodeFlow

[denelon]

wingetcreate doesnt' necessarily need to serialize as JSON. YAML serialization is fine as long as wingetcreate knows how to transform the YAML file-based manifests to the JSON expected by a WinGet source REST endpoint.

The same would be true in terms of the upgrade scenario where the package ID and source are REST based. The transformation from JSON to YAML could happen inside wingetcreate.

[denelon]

I'm not opposed to this, but we should be careful in terms of how we decide which format wingetcreate defaults to and how we do any of the transformations.

[mdanish-kh]

wingetcreate will always default to YAML serialization. That is the default --format value and also the default user setting value.

Moreover, submitting anything other than YAML to the main community repository has also been blocked as part of this PR.

I'm not opposed to closing this if we don't want this, but there could still be value in this PR. The refactorings made to the Serialization flow here may make it easier for a future REST-source implementation. The target of this PR was not really REST implementations but more of private GitHub repositories that want JSON as their output manifests (as was mentioned in the original feature request)

[denelon]

No worries :)

If @ryfu-msft is good with it, then I am too.

[ryfu-msft]

@mdanish-kh, will take a look at this soon.

I want to create a new release for winget-create to support 1.6 manifests first since there are a lot of your new features in there. This will be included in our next 1.7 release.

[ryfu-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

I have merged microsoft/winget-pkgs-submission-test#4784 so that these tests will pass. We will need to get this in first so that #512 can pull in latest changes.

[ryfu-msft]

Really awesome feature :)