Automate release pages

Currently, releases need to be updated by hand via assets/js/releaseData.js. Additionally, alphas and betas aren't represented at all. We could automate this.

## Alphas

- [ ] Get an API which gets the latest build from Github and offers it to download (similar to https://github.com/oprypin/nightly.link )
- [ ] Do the same for the qt branch once that's testing-ready
- [ ] Create a /builds page on which they can live (similar to https://builder.blender.org/download/daily/)

## Betas

- [ ] Create a GH action which publishes a beta release on Github
- [ ] and enables temporary elements to the homepage pointing towards the beta

## Releases

- Create a GH action which publishes releases to
- [x] winget
- [ ] Github releases
- [ ] musehub
- [ ] Fosshub
- [ ] MS store
- [ ] (if legally possible) Apple App store
- [ ] (if we want to maintain it) Snapcraft
- [ ] (if we want to maintain it) Flathub
- [ ] updates releaseData.js
- [ ] and hides the temporary beta element from the homepage

Inizia leggendo assets/js/releaseData.js e suddividi la richiesta in un workflow specifico per una release, una beta o un’alpha prima di apportare modifiche. L’issue menziona GitHub APIs, GitHub Actions, una pagina /builds e diverse destinazioni di distribuzione, ma non identifica i test né una prima milestone ben delimitata; il lavoro sarà considerato completato quando sarà stato concordato un ambito e saranno stati completati i relativi elementi della checklist.

Scritto dal modello di indicizzazione a partire dal testo della issue.