Add CI action for publishing package to WinGet

[mdanish-kh]

• Related to Publish to package manager registries #196

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.

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. I see a fork already created https://github.com/DaveTryon/winget-pkgs so I'm assuming that would be the one used here
2. Create a public access token (classic) with public_repo scope from the user account where the fork exists.
3. Store the created token in a repository secret here with the name WINGET_GITHUB_TOKEN

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

[DaveTryon]

Thanks for the suggestion, @mdanish-kh! Our release process goes through an ADO release pipeline, so this isn't something that we would implement via a GitHub action. That said, we'll see if we can convert our WinGet release (currently a manual process) to an automated step in the release pipeline.

[mdanish-kh]

@DaveTryon Understood! wingetcreate docs has a sample ADO task too if you're interested

https://github.com/microsoft/winget-create/blob/aebe9dfbd8c3c4ec5199be4032c3553b4986b851/pipelines/azure-pipelines.release.yml#L267-L283