ci: Add winget-releaser

[ottnorml]

fix #269

[ottnorml]

Since the new publish-to-winget job depends on the publish job that only runs when there is a new version, I couldn't test my changes without releasing version 1.4.0.

[roldanjr]

Since the new publish-to-winget job depends on the publish job that only runs when there is a new version, I couldn't test my changes without releasing version 1.4.0.

We'll wait for other bug fixes for batch release. Thanks for your contribution @ottnorml 🙇🏼

[ottnorml]

Since the new publish-to-winget job depends on the publish job that only runs when there is a new version, I couldn't test my changes without releasing version 1.4.0.

We'll wait for other bug fixes for batch release. Thanks for your contribution @ottnorml 🙇🏼

Fortunately, I did find a way to test the new action, and I noticed a few bugs that should be fixed now. 😁💪

[ottnorml]

I opened a new PR to add v1.3.0 and its new installers for arm64 and x64 (see microsoft/winget-pkgs#121172).

[roldanjr]

Hi @ottnorml should we wait for this to pass the remaining CI checks?

I don't have Windows installed right now, maybe you can request @sekwah41 to review and test it once the issue on the winget-pkgs has been resolved.

[ottnorml]

Hi @roldanjr,
I have asked for a retry of the security check. The fact that the old PR is not yet merged does not affect this PR, because the release job will create a new independent PR for the new version of Pomaz. So there is nothing that would block the merging of this PR. 😁

[roldanjr]

LGTM!