Scoop bucket and winget manifest #58

Why

Windows users are told to "download the zip and put apic.exe on your PATH". scoop install and winget install are the two commands Windows developers actually use, and goreleaser can publish both.

What

• Create dataGriff/scoop-bucket; add scoops: to .goreleaser.yaml (bucket repo, description, license, bin: apic.exe), using the same tap token or a second fine-grained PAT.
• Add winget: to .goreleaser.yaml producing a manifest PR against microsoft/winget-pkgs (publisher dataGriff, package dataGriff.apic); this needs a fork and a PAT with public_repo scope. The first submission is manual review on Microsoft's side; document the lag.
• README and getting-started Windows tab: scoop bucket add datagriff https://github.com/dataGriff/scoop-bucket && scoop install apic and winget install dataGriff.apic.

Where

.goreleaser.yaml, .github/workflows/release.yml, README.md, docs/getting-started.md, docs/index.md, docs/faq.md (Windows answer).

Tests

Snapshot render of the Scoop manifest; a manual install on a Windows runner (a CI job on windows-latest that installs from the bucket after release is a nice follow-up).