Feature/winget: adds TriliumNext Notes to winget community package repo

[maphew]

Addresses TriliumNext/Trilium#5320, TriliumNext/Trilium#5086. TriliumNext.Notes is now in the Winget Community Package Repository.

A full implementation will need integration with Github Actions. I don't think I can do that from a fork, however .github/workflows/release-winget.yaml includes a stub for that (docs: https://github.com/vedantmgoyal9/winget-releaser)

I believe the next step would be for someone with relevant permisssions to setup a github classic api token with just public_repo scope for winget in .env - (ref).

This PR creates a new top level folder ./release. Feel free to move if there is a better home. The yaml files are documentation/examples in case the winget manifest needs to be rebuilt. The authoritative files are at https://github.com/microsoft/winget-pkgs/tree/master/manifests/t/TriliumNext/Notes

[JYC333]

I see some package version, release date, and install url point to specific version. Does that mean we need to update manually everytime? Or it can change to some autonomous way?

[maphew]

I believe most folks use a Github Action to update the release package specifics upon a stable release, and that it needs to be done by someone with commit acces to the main repository and abilty to create a release. From the Winget Release 'getting started' notes:

At least one version of your package should already be present in the Windows Package Manager Community Repository. The action will use that version as a base to create manifests for new versions of the package.

• You will need to create a classic Personal Access Token (PAT) with public_repo scope. New fine-grained PATs aren't supported by the action. Review [Feature/Idea]: Fine-grained tokens seem to support the GraphQL API now vedantmgoyal9/winget-releaser#172 for information.
• Fork microsoft/winget-pkgs under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present.
• Add the action to your workflow file (e.g. .github/workflows/.yml).

Important:
The action will only work when the release is published (not a draft), because the release assets (binaries) aren't available publicly until the release is published.

[eliandoran]

@maphew , thank you for your contribution as it helped us kickstart the initial PR to WinGet.

Closing in favor of #1617, to handle automatic updates on release.