Changes goreleaser to use generate app token

[bomoko]

This PR moves us from using a github PAT to generating a token via a github app

General Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

[Copilot]

Pull request overview

This PR updates the release workflow to stop using a long-lived GitHub PAT and instead generate a short-lived GitHub App installation token for GoReleaser, aligning the release process with app-based authentication.

Changes:

• Added a “Generate App Token” step using actions/create-github-app-token@v3.
• Switched GoReleaser to use the generated token (steps.app-token.outputs.token) instead of secrets.GH_ACTION_PAT.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/workflows/goreleaser.yaml:56

• This job currently relies on the repository’s default GITHUB_TOKEN permissions. Since the release/publish operations are now done via the GitHub App token, it’s safer to explicitly scope the workflow GITHUB_TOKEN for this job to the minimum needed (typically contents: read for actions/checkout).

        name: Generate App Token
        id: app-token
        uses: actions/create-github-app-token@v3

[rocketeerbkw]

Actions config matches app.