ci: add goreleaser release pipeline and analyze.sh installer

[blimmer]

Adds the release pipeline for patchwave-analysis, modeled on planbridge/patchwave.

What's here

• goreleaser (.goreleaser.yaml): bun --compile for darwin arm64/x64 + linux x64, macOS signing/notarization (gated on the AWS-provided MACOS_SIGN_P12), version-less archive names, and ships analyze.sh as a release asset. Uses dist: dist-release so it doesn't collide with the dist/report-web/ asset the before-hook builds.
• release-please (release-please-config.json + manifest + release-please.yml): release-type: node, so the package.json bump flows into the compiled binary's version. Uses the CB PR-automation app token so the release tag triggers release.yml.
• release.yml: tag-triggered → test → goreleaser, assuming the AWS release role via OIDC (fetch-release-secrets reads the signing secrets from SSM/Secrets Manager).
• scripts/analyze.sh (+ test): one-off runner — downloads the platform binary from the latest release, checksum-verifies, runs it, and discards it. Reconnects /dev/tty so the interactive prompts work over curl | bash.
• zizmor.yml + lint-pr-title.yml: workflow security audit + conventional-commit PR titles.
• README "Run it" now leads with bash -c "$(curl -fsSL https://patchwave.ai/analyze.sh)".

Notes

• patchwave.ai/analyze.sh 404s until the first release exists (the redirect targets releases/latest/download/analyze.sh). The redirect itself lives in a companion change on contextbridge/patchwave.
• The README "Options" section still documents the current flag-based CLI; it'll reconcile when the interactive CLI lands.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.