Switch to OIDC auth for publishing to NPM registry.

[MathieuGilbert]

NPM announcement strongly encouraging the use of OIDC, and the disabling of long-lived tokens mid-November.

Is this PR a bug fix, new feature, or security update?

• Change to NPM publish auth.
• Security update: 7 vulnerabilities (1 low, 2 moderate, 3 high, 1 critical)

Please describe this pull request:

• This repo's workflow has already been added as a trusted publisher for GitHub Actions.
• Applied the suggested auth changes in the workflow.
• Also ran npm audit fix to address the warnings.

PR Review Checklist

• I have passing tests run via npm run test with a 100% coverage threshold
• I have updated the version in package.json
• I have updated any relevant documentation in README.md, .github, etc.
• I have not included any secret values or links to internal AMA URLs in my commits or PR message

[amaValeriya]

I don't have access to npm to verify what you mentioned in the test steps, but I have no reason not to trust you.