Update NPM token secret in release workflow

[hubertott]

Description of the proposed changes
Feels like we should be using the GH Global secret thats 3 months old vs the 5yr old one specific to this repo?

Screenshots (if applicable)

Notes to PR author

⚠️ Please make sure the changes adhere to the guidelines mentioned in our contribution guide.

Notes to reviewers

ℹ️ When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback

[AdamJHall]

This should work as is, but we may need to add an npm upgrade step like Will did here: https://github.com/aligent/cdk-constructs/pull/1600/changes and switch out to auth this repo as a "trusted publisher" REF: https://docs.npmjs.com/trusted-publishers

[hubertott]

This should work as is, but we may need to add an npm upgrade step like Will did here: https://github.com/aligent/cdk-constructs/pull/1600/changes and switch out to auth this repo as a "trusted publisher" REF: https://docs.npmjs.com/trusted-publishers

Strangely this part is missing 🤔

The critical requirement is the id-token: write permission, which allows GitHub Actions to generate OIDC tokens. Learn more in GitHub's OIDC documentation.

Update:
🤦🏽 Ignore me.. it was already there 😬