chore(npm): Update release npm action to stop using tokens

[gnbm]

What is the current behavior?

• Some dependencies were outdated
• The publish action required a static npm token and didn’t configure the registry for OIDC.

GitHub Issue Number: N/A

What is the new behavior?

• Updated test tooling:

  • find-up to ^8.0.0
  • @stencil/core to ^4.38.2
  • @types/eslint to ^9.6.1
  • @types/jest to ^30.0.0
  • @types/node to ^24.9.2
  • @typescript-eslint/eslint-plugin to ^8.46.2
    -@typescript-eslint/parser to ^8.46.2
    -cspell to ^9.2.2
    -esbuild to ^0.25.11
    -eslint to ^9.38.0
    -eslint-config-prettier to ^10.1.8
    -eslint-plugin-jsdoc to ^61.1.11
    -eslint-plugin-simple-import-sort to ^12.1.1
    -eslint-plugin-unused-imports to ^4.3.0
    -jest to ^30.2.0
    -prettier to ^3.6.2
    -rimraf to ^6.0.1
    -ts-jest to ^29.4.5
    -typescript to ^5.9.3

• Configured Node via actions/setup-node@v6 with the npm registry to trigger trusted publishing.

• Removed .npmrc token writes and relied on OIDC-issued credentials.

• Updated release workflows to call the reusable action without passing secrets.

• Kept existing build artifact handling and version bumping untouched.

Documentation

• N/A

Does this introduce a breaking change?

• Yes
• No

Testing

• Local runs (Windows):

  • npm ci
  • npm run format
  • npm run lint
  • npm run spellcheck
  • npm run build
  • npm run test
  • Verified output shows all suites passing
    • Test Suites: 2 passed, 2 total
    • Tests: 6 passed

• Not run (workflow-only change).

Other information

• N/A