WINDOWS: Build a scoop distribution for Windows - reference Bo Zhang's prototype

[Lutra-Fs]

I could create another bucket to store only rattleng. The best would be submitting to scoop's extra bucket. However I don't think we have met the criteria.

[Lutra-Fs]

• [ ] Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 100 stars and/or 50 forks)
• [ ] English interface (or at least English documentation)
• [ ] Latest stable version
• [ ] Full version (i.e. not a trial version)
• [ ] Fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts

[gjwgit]

We will need to add a github actions workflow to add a script to create a scoop installer.

[Lutra-Fs]

We will need to add a github actions workflow to add a script to create a scoop installer.

A Scoop manifest is a JSON file describing how to install a Windows program using the Scoop package manager. It includes details like version, download URL, and installation instructions. A Scoop bucket is a repository of these manifest files. It's typically a separate Git repo containing manifests for multiple applications and follows a defined structure. We should not store the manifest in the app's repo primarily because when a Scoop user adds a bucket, Scoop clones the entire repo. Keeping manifests separate avoids unnecessary cloning of the app's source code and development history. Instead, manifests are usually added to dedicated bucket repos or community-maintained buckets. This approach simplifies manifest management and improves the user experience when installing applications via Scoop. For example, I have a manifest for RattleNG in my personal bucket. Typically, bucket maintainers use GitHub Actions to automatically check for new versions and update the manifest by calling APIs or using other methods. This automation helps keep the manifests up-to-date without manual intervention.