Add action for publishing package to WinGet

[mdanish-kh]

This PR proposes to add a GitHub action for submitting the latest stable release to WinGet as it gets published. microsoft/winget-create is used as the tool for submitting the latest package.

• Resolves Set up CI to publish to WinGet #80

Steps needed from maintainers

If the maintainers approve of these changes, they will need to do the following before merging this PR:

1. Fork microsoft/winget-pkgs under a personal or bot account.
2. Create a personal access token (classic) with public_repo scope from the user account where the fork exists.
3. Store the created token in a repository secret with the name WINGET_GITHUB_TOKEN

For reference, maintainers may see similar implemented actions in the following repos:
Terminal, PowerToys, Oh-my-posh, coder/coder

Validation

You can download wingetcreate via https://aka.ms/wingetcreate/latest or winget install wingetcreate and validate that a command such as the following will generate a manifest. I have omitted --submit which would submit a PR to the main repo. You can specify your own fork too for testing with wingetcreate settings command and then use --submit

wingetcreate update HTTPToolKit.HTTPToolKit `
  --version 1.19.4 `
  --urls "https://github.com/httptoolkit/httptoolkit-desktop/releases/download/v1.19.4/HttpToolkit-installer-1.19.4.exe|x64" `
  --token <token>

[CLAassistant]

All committers have signed the CLA.

[pimterry]

Thanks @mdanish-kh!

For now, I've created a entire separate github user to hold the forked repo, to limit the classic PAT that's required here. Do you know if GitHub's fine-grained per-repo PATs will be supported in future so that that's not required?

[mdanish-kh]

Yes, I believe there's an open issue over at winget-create repository tracking this work

• ERROR: Resource not accessible by personal access token microsoft/winget-create#470