fix: Revert to previous flow to unblock release

[jackw-phantom]

Summary by CodeRabbit

• Chores
  • Updated release workflow infrastructure, including changes to Node.js environment configuration and dependency installation processes.
  • Modified authentication and permission settings in the release pipeline.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub Actions release workflow is reconfigured to downgrade Node.js from 24.x to 20.x, add yarn caching, switch from global npm version enforcement to immutable yarn installs, replace NPM provenance with token-based authentication, and remove unused workflow permissions and concurrency settings.

Changes

Cohort / File(s)	Summary
Node.js & Setup Configuration .github/workflows/release.yml	Downgraded Node.js from 24.x to 20.x; added yarn cache and registry URL configuration to setup-node step
Dependency Installation .github/workflows/release.yml	Removed global npm version enforcement (npm install -g npm@^11.8.0); changed yarn to yarn install --immutable for stricter dependency locking
Authentication & Permissions .github/workflows/release.yml	Replaced NPM_CONFIG_PROVENANCE environment variable with NPM_TOKEN secret in changesets step; removed id-token workflow permission; removed top-level concurrency setting

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change as reverting the release workflow to unblock publishing, which aligns with the workflow modifications shown in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}