fix(ci): update npm for OIDC trusted publishing

[assagman]

Summary

• Add npm install -g npm@latest before publish step
• npm 11.5.1+ required for OIDC trusted publishing

Root Cause

GitHub Actions runners have outdated npm, causing:

npm notice Access token expired or revoked
npm error 404 Not Found

After Merge

Re-run Publish Release workflow to publish v0.10.1 to npm.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[Copilot]

Pull request overview

This PR updates the GitHub Actions release workflow to install the latest npm version before publishing to npm. This addresses an issue where outdated npm versions on GitHub Actions runners lack support for OIDC trusted publishing (requires npm 11.5.1+), which was causing authentication failures.

Changes:

• Added a new workflow step to globally install the latest npm version before the publish step

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Using npm@latest may introduce instability if future npm versions have breaking changes. Consider pinning to a specific version range (e.g., npm@^11.5.1) to ensure OIDC support while maintaining predictable behavior.

Suggested change

	run: npm install -g npm@latest
	run: npm install -g npm@^11.5.1

[Copilot]

Consider adding an inline comment documenting the minimum required npm version (11.5.1+) to help future maintainers understand the version requirement for OIDC trusted publishing.

Suggested change

	run: npm install -g npm@latest
	run: npm install -g npm@latest # Ensure npm >= 11.5.1 for OIDC trusted publishing