Adding GitHub action for winget-releaser

[assarbad]

Summary:

This would conclude #848 (which also requires microsoft/winget-pkgs#184453 to be merged).

Description for the changelog:

• It is now possible to install OWASP Threat Dragon with WinGet, using winget install -e --id OWASP.ThreatDragon or subsequently keep it up-to-date with winget upgrade -e --id OWASP.ThreatDragon

Other info:

Below follows the commit message in full:

---

• This is meant to automate releases to winget-pkgs
• Resolves winget support would be great #848 and should work as soon as New package OWASP.ThreatDragon 2.2.0 microsoft/winget-pkgs#184453 has been merged (baseline manifest for the 2.2.0 version)
• DO NOT MERGE BEFORE PREREQUISITES ARE IN PLACE (see below)

Instructions for prerequisites

The WINGET_TOKEN needs to be created and registered in the repo which does the release. For good measure we need to clone winget-pkgs on the same user (or org) or set via fork-user it as per the README for winget-releaser.

Configure the Pull app to keep the winget-pkgs fork in sync with its upstream.

That winget-pkgs fork is going to be the source of the PR filed at microsoft/winget-pkgs and the PRs are being opened on behalf of the owner of the used token.

1. Head to https://github.com/settings/tokens and create a new (classic) personal access token with only the public_repo scope activated for it
2. In https://github.com/OWASP/threat-dragon/settings/secrets/actions create a secret named WINGET_TOKEN (as per vedantmgoyal9/winget-releaser)
3. Merge this PR
4. Create a (subsequent) release

[jgadsden]

hello @assarbad , I have created WINGET_TOKEN which contains the personal access token

[jgadsden]

thanks @assarbad , all looks good for merging - do we wait for microsoft/winget-pkgs#184453 to have been merged first?