ci: stage npm releases before publishing

[JoviDeCroock]

Summary

• Switch the release workflow from direct changeset publish to staging the package with npm stage publish.
• Add a small staging helper that skips already-published versions, derives the dist-tag from the package version, stages with the configured public access, and surfaces stage IDs when npm returns them.
• Bump the workflow npm install to npm@^11.15.0, which is required for staged publishing.

Why

This keeps CI responsible for preparing the release artifact, but moves the final public publish behind maintainer approval with 2FA via npm stage approve <stage-id> or npmjs.com.

[changeset-bot]

⚠️ No Changeset found

Latest commit: cb25e94

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