feat: distribute the CLI via Scoop

[NickJosevski]

Part of #37 — Scoop was the last unticked box on the package manager list.

Change

Adds a scoops block to .goreleaser.yaml and a deployment process step that pushes the generated manifest.

Scoop is served from a bucket repository we own, OctopusDeploy/scoop-octopus, rather than the official ScoopInstaller/Main bucket, which only accepts widely-adopted tools (500+ stars, 150+ forks). This mirrors the homebrew tap: goreleaser generates the manifest but skip_upload stops it publishing, and the Octopus deployment process commits it into bucket/.

Unlike the homebrew step, the scoop step commits straight to the default branch instead of raising a PR — a bucket is machine-maintained, there is nothing for a human to review.

The manifest covers both 64bit and arm64, so Scoop becomes the only Windows package manager through which we ship a native ARM build (winget and chocolatey are x64 only).

Why draft

The bucket repository has to exist, and Publish:Scoop:Username, Publish:Scoop:UserEmail and Publish:Scoop:ApiKey have to be set on the Octopus project, before this can be merged. Nothing here is verifiable end to end until a release runs.

🤖 Generated with Claude Code

[NickJosevski]

The first release through this step can never publish the manifest: in a fresh clone the copied bucket/octopus-cli.json is a new untracked file, and git diff-index HEAD only compares tracked files — it exits 0 and the || branch is skipped, so nothing is committed or pushed and the step still goes green. Because every deploy starts from a fresh --depth 1 clone, this repeats on every release until someone commits the manifest to the bucket repo by hand. Even when the guard does fire, git commit -a also only stages tracked-file changes, so it would fail on an untracked manifest anyway ("nothing added to commit but untracked files present").

Suggested fix — stage first, then guard on the index:

git add bucket
git diff-index --quiet --cached HEAD || (git commit -m "Update for release $packageVersion" `
    && git push --repo $origin `
)

[NickJosevski]

Unlike the sibling homebrew step, this script sets no $ErrorActionPreference = "Stop" and never checks $LASTEXITCODE, so failures degrade into a silent green step instead of a clean error. Concretely: if Copy-Item fails (bad path, package layout change), the error is non-terminating, git diff-index then sees a clean tree and exits 0, and the deployment reports success having pushed nothing. A failed git clone cascades similarly — Set-Location fails non-terminating and the rest of the script runs in the wrong directory.

Suggest mirroring the homebrew step: $ErrorActionPreference = "Stop" at the top, plus if ($LASTEXITCODE -ne 0) { throw "..." } after the clone and push.