[Build] Add Windows targets to goreleaser + Windows CI job

[DecampsRenan]

Why

Once the code runs on Windows, the release pipeline must ship Windows binaries and CI must catch Windows regressions. This sub-issue extends goreleaser to produce windows/amd64 and windows/arm64 archives, and adds a Windows job to the GitHub Actions matrix. Blocked by [Compat] and [Audio].

Topics

Goreleaser configuration

• windows added to goos, amd64 + arm64 kept under goarch
• .zip archive format for Windows (instead of .tar.gz)
• checksums.txt includes Windows artifacts

CI matrix

• windows-latest runner added to the test workflow
• Existing test suite passes on Windows
• Lint and build steps run on Windows

Release verification

• A pre-release tag produces working Windows archives attached to the GitHub release
• Downloaded binary runs on a clean Windows machine without Go installed