fix(ci): isolate GitHub write token to release job

[JSONbored]

Motivation

• Remediate a workflow-level elevation where contents: write left a write-scoped github.token available during dependency/tooling steps in .github/workflows/npm-publish.yml.
• Prevent the default actions/checkout behavior from persisting potentially dangerous write credentials into local git config before untrusted package/tooling execution.
• Ensure GitHub release creation (which requires write) is executed in a minimal, isolated job after validation and publishing complete.

Description

• Changed the workflow-level permission in .github/workflows/npm-publish.yml from contents: write to contents: read.
• Scoped the publish job with permissions: contents: read and id-token: write so tooling steps run with read-only repo access.
• Added persist-credentials: false to the actions/checkout step to avoid writing the token into git config before npm ci/tests/build steps.
• Moved the GitHub release creation into a new github-release job that runs needs: publish and is the only job granted contents: write and which uses GH_TOKEN: ${{ github.token }}.

Testing

• Ran git diff --check which produced no whitespace or diff-check failures and succeeded.
• Validated YAML syntactic correctness with ruby -e 'require "yaml"; YAML.load_file(".github/workflows/npm-publish.yml")' which succeeded.
• Attempted npm run actionlint but it was blocked by network/DNS resolution in the environment (github-actionlint: getaddrinfo EAI_AGAIN github.com).

---

Codex Task