Add action for publishing package to WinGet

[mdanish-kh]

[ ] Please update master_changes.md file with your changes. - Will do if changes look good to the maintainers

Description

I just saw an issue opened by a maintainer (cc @dra27) at winget-pkgs: https://github.com/microsoft/winget-pkgs/issues/192924. Thought it would be a good idea to suggest adding an action to do this automatically on every new version released

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.
2. Create a public access token (classic) with public_repo scope from the user account where the fork exists.
3. Create a repo secret in this repo with the name WINGET_GITHUB_TOKEN

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

[dra27]

Thanks for this - I expect it’ll take me a while to actually action it all, but I hope we can put this in place for the 2.4 release next year! It’ll want adapting to double-check that the artefact is actually present (because the Windows binary gets added to the release after it’s published), but I’ll be very happy to sort that out.

[kit-ty-kate]

I believe this PR is no longer considered for inclusion. Considering security issues and the otherwise sometimes prohibitive cost in terms of maintenance/stress of such an automated script, this doesn't seem very appealing to me.

Instead the publishing to winget step was added to the list of things to do at every release and as release manager for the past two releases i gotta say doing it this way was pretty easy and reasonably fast.

Thanks for the suggestion though!

[mdanish-kh]

That's okay, I can empathize with the mentioned challenges :)