chore: switch release workflow to npm trusted publishing

[mrice32]

Summary

• Replace NPM_TOKEN secret with OIDC-based npm trusted publishing (id-token: write permission)
• Upgrade Node from 20.x to 22.x and add npm install -g npm@latest step (npm >= 11.5.1 required for OIDC)
• Add registry-url to actions/setup-node to enable OIDC auth flow

Trusted publishing has been configured on npmjs.com for @across-protocol/app-sdk.

Test plan

• Merge and verify the next changesets release publishes successfully via OIDC

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: d061607

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
toolkit-example	Ready	Preview, Comment	Feb 25, 2026 9:00pm