chore: add explicit permission on release workflow

[remyleone]

Potential fix for https://github.com/scaleway/scaleway-cli/security/code-scanning/51

The best way to fix this problem is to add an explicit permissions block to the workflow. Ideally, you should set this block at the top (workflow) level so that it applies to all jobs, unless a particular job requires more specific permissions—in which case, override at the job level. As a minimal and safe default, use contents: read. If a job (such as goreleaser, which may need to create GitHub Releases or upload assets) requires additional permissions (such as contents: write or packages: write), configure these specifically for that job. Since the wasm job seems only to publish to npm and not interact with the GitHub API, it can probably use only contents: read, but goreleaser may require more.

For the minimal fix, add permissions: contents: read at the root workflow level. For greater robustness, consider specifying job-level permissions: goreleaser with contents: write, wasm with contents: read.

Files/regions to change:

• Add a permissions: block after the name: at the top of .github/workflows/release.yml.
• Optionally, add a more permissive permissions: block under the goreleaser: job if it requires it, otherwise rely on the root-level block.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.