Add Winget Releaser workflow

[sitiom]

This action automatically generates manifests for WinGet Community Repository (microsoft/winget-pkgs) and submits them.

I have already created a PR to add ElectronMail to Winget; this workflow will be used to update it.

Before merging this:

1. Add a PAT with public_repo scope as a repository secret named WINGET_TOKEN (or rename the secret name in the workflow).

2. Fork https://github.com/microsoft/winget-pkgs under @vladimiry. The action will use that fork for making a branch and creating a PR with the upstream winget-pkgs repository on every release.
3. Sign the Contributor License Agreement for winget-pkgs as you (the PAT owner) will be a first-time contributor.

If you would like to read about this action further, the documentation is here, and the source code is here.

If you want to see an example of a PR created using this action, see microsoft/winget-pkgs/pulls (Pull request has been automatically created using 🛫 WinGet Releaser).

[vladimiry]

Thanks for the effort towards automating things and for the detailed instructions, but at this time I tend to reject the PR.

Currently, none of the listed in the README package repositories requires the project to include/maintain repo-specific stuff, and I prefer it to stay this way. So if some repo wants to include the app package, that would be an independent pulling strategy.

Besides, at the moment, there is no interest in signing some CLA.

CC @joshirio / @hiddeninthesand

[sitiom]

@vladimiry You do maintain the flatpak package, right? What's the difference with this one?

Edit: I see. You maintain it manually, but it can use some automation since you control the package.

[vladimiry]

You do maintain the flatpak package, right? What's the difference with this one?

This is a different project which is pulling stuff from here. So technically, ElectronMail project knows nothing about it (pulling vs pushing strategy).