CI: add Winget Releaser workflow

[sitiom]

• Continuation of https://github.com/fastfetch-cli/fastfetch/issues/320#issuecomment-1404822340

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

Fastfetch has been added to Winget (https://github.com/microsoft/winget-pkgs/pull/154718), and this workflow will be used to update it.

Before merging this:

1. Add a classic PAT with public_repo scope as a repository secret named WINGET_TOKEN.

2. Fork https://github.com/microsoft/winget-pkgs under @fastfetch-cli. The action will use that fork for making a branch and creating a PR with the upstream winget-pkgs repository on every release.
3. Install Pull on the winget-pkgs fork to ensure that it is constantly updated.

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).

[CarterLi]

@LinusDierheimer I don't have the permission. Can you help with this?

[sitiom]

@CarterLi The fork-user can be set to your account instead if that's what you want

[CarterLi]

I have the permission to create repos in @fastfetch-cli. I don't have the permission to add personal tokens in fastfetch repo

[sitiom]

I noticed that fastfetch-windows-aarch64.zip is being put manually in the releases; that would be a problem for this action which expects all assets to be available on release.

[CarterLi]

Yeah. I haven't found a way to build windows-aarch64 binaries with Github Actions. I always build them manually.

[LinusDierheimer]

@CarterLi Made you an admin, does it work now?

[sitiom]

Yeah. I haven't found a way to build windows-aarch64 binaries with Github Actions.

Perhaps I should add a workflow_dispatch trigger so that you can run it manually.

[CarterLi]

I'm happy with current situation. Closing