ci: include token permissions needed to create artifact content of a release

[zimeg]

📚 https://goreleaser.com/quick-start/

To release to GitHub, you'll need to export a GITHUB_TOKEN environment variable, which should contain a valid GitHub token with the repo scope. It will be used to deploy releases to your GitHub repository. You can create a new GitHub token here.

The minimum permissions the GITHUB_TOKEN should have to run this are write:packages

  ⨯ release failed after 18s                 error=scm releases: failed to publish artifacts: could not release: POST https://api.github.com/repos/zimeg/git-coverage/releases: 403 Resource not accessible by integration []

https://github.com/zimeg/git-coverage/actions/runs/14818431455/job/41602083658#step:4:183

🔍 https://github.com/goreleaser/example-zig/blob/6bfeba3587e169ff31cba2da32854da025600937/.github/workflows/release.yml#L10-L11

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.59%. Comparing base (3e78b6d) to head (63d7a8d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   94.59%   94.59%           
=======================================
  Files           1        1           
  Lines          37       37           
  Branches       37       37           
=======================================
  Hits           35       35           
  Misses          2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zimeg]

🍎 https://support.apple.com/guide/mac-help/open-a-mac-app-from-an-unknown-developer-mh40616/mac