fix(ci): authenticate CLI npm publish

[Aymericr]

What does this PR do?

Passes the repository NPM_TOKEN to the CLI publish step, matching the other package-specific publish steps. The CLI beta release reached npm publish but failed with npm 404/permission because this step had no token environment.

How to test

1. Inspect the release workflow diff.
2. Rerun the CLI beta release after merge; its recovery-safe version check will publish 1.0.0-beta.2 and then commit/tag the version bump.

Screenshots / screen recording

Not applicable.

Checklist

• I've tested this locally with bun dev
• My code follows the existing workflow pattern
• I've updated relevant documentation
• This PR targets the main branch

---

Note

Low Risk
Workflow-only change that adds missing npm auth to an existing publish step; no application or runtime behavior changes.

Overview
The Publish CLI job in release.yml now sets NODE_AUTH_TOKEN from secrets.NPM_TOKEN, the same pattern used by the other package publish steps.

Without this, CLI releases could reach npm publish and fail with registry permission/404 errors because npm had no credentials for that step.

^{Reviewed by Cursor Bugbot for commit 7957fff. Bugbot is set up for automated code reviews on this repo. Configure here.}

[pascal]

I hit an error while handling your request (Model unavailable on AI Gateway free tier: Free tier users do not have access to this model. Upgrade to paid credits at https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai%3Fmodal%3Dtop-up for unrestricted…).

Please try again, rephrase, or reach out if it keeps failing.

Error id: 72b04ff6-6902-4991-8fd1-6ba882f229d9