Revolutionizing CI Workflows: NPMJs.com "Trusted Publisher" Authentication Now Supported!

Cutting-edge changes to enhance package releases and streamline authentication processes in the latest update.

Commit Details:

CI changes to support npmjs.com "trusted publisher" auth (#2668) ## Why is this change needed? Describe why this issue should be fixed and link to any relevant design docs, issues or other relevant items. ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review_ - [ ] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard - [ ] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets) - [ ] PR has been tagged with a change label(s) (i.e. documentation, feature, bugfix, or chore) - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. <!-- start pr-codex --> --- ## PR-Codex overview This PR updates the CI workflow for package releases, including changes to permissions, Node.js version, and the `changesets/action` version, while also modifying the handling of NPM tokens. ### Detailed summary - Added permissions for `contents` and `id-token` in the workflow. - Updated `node-version` from `18` to `22.x`. - Set `registry-url` to `https://registry.npmjs.org`. - Upgraded `changesets/action` from `v1` to `v1.6.0`. - Changed `NPM_TOKEN` to an empty string. - Enabled `NPM_CONFIG_PROVENANCE`. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->