Add a Winget Releaser workflow

[sitiom]

The winget-releaser action automatically generates manifests for the
Winget Community Repository and submits them.

I suggest adding Dependabot to keep the action up to date. There were
many cases where the action was failing due to an outdated version.

Closes #14795

[zadjii-msft]

Please ensure that the release tag matches the full package version of the msixbundle

OH BOY uh, that might be hard. We actually just switched away from doing that, because that was confusing. See #14106 for some discussion here. We may need to pursue the "Workflow with implementation of custom package version" option here

[sitiom]

Hmm, extracting the full version from the release asset name would work too.

[sitiom]

Hmm, extracting the full version from the release asset name would work too.

Done. The tag name shouldn't be a worry now.

[zadjii-msft]

https://dev.azure.com/ms/terminal/_build/results?buildId=436098&view=logs&j=f3a2b39c-7194-5ef8-38f6-25d401474452&t=f15c8814-6a22-5381-efd1-6ff85efcd4b6&l=12300

    72>Done Building Project "C:\a\_work\1\s\src\cascadia\TerminalAzBridge\TerminalAzBridge.vcxproj" (build target(s)).
##[error]C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(497,5): Error MSB4181: The "MSBuild" task returned false but did not log an error.
   100>C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(497,5): error MSB4181: The "MSBuild" task returned false but did not log an error. [C:\a\_work\1\s\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj]
   100>Done Building Project "C:\a\_work\1\s\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj" (default targets) -- FAILED.
     2>Done Building Project "C:\a\_work\1\s\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj.metaproj" (default targets) -- FAILED.

Your PR should not have touched this at all... Something about our CI looks busted. I'll take a look

[sitiom]

What did I touch? I just added a file 😅

[zadjii-msft]

Nah no this wasn't you, this is the There is a circular dependency in the target dependency graph issue, #14581. I'll kick the build, it usually goes away after (a couple) retries

[zadjii-msft]

@msftbot make sure @DHowett signs off on this

[zadjii-msft]

y'know "microsoft-github-policy-service" just doesn't roll off the tongue like msftbot did.

@microsoft-github-policy-service make sure @DHowett signs off on this

[DHowett]

Moved notes from PR body

---

Before merging this:

1. @DHowett Please create a classic PAT with public_repo scope and add it as here as a repository secret named WINGET_TOKEN.

2. I also noticed https://github.com/DHowett/winget-pkgs is outdated. Please install Pull on the fork to ensure that it is kept up to date.

Additional Notes:

You can test out the action inputs in this playground.

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

Validation Steps Performed

Tested the action inputs in the playground.

---

I'll take the to-do, and probably use the bot service account we have for it. Thanks so much for doing this!

[DHowett]

Thanks so much for doing this!

[sitiom]

I'll take the to-do, and probably use the bot service account we have for it. Thanks so much for doing this!

Don't forget to change the fork-user input to the bot account when you do so (or you probably should have done the prerequisites before merging this).

[DHowett]

HAHA OOPS. Thanks/sorry