chore(ci): use OIDC token for trusted publishing to npm

[hainenber]

PR Checklist

• Addresses an existing open issue: fixes 🛠️ Repo: use OIDC for publishing #5611
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Removes the need for long-lived npm token used for publishing new version and its subsequent need for periodic rotation.

@mark-wiemer you'll need to follow this guide though, just a bit more paperwork to get things in motion D

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.53%. Comparing base (3ea1578) to head (031c417).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5610   +/-   ##
=======================================
  Coverage   93.53%   93.53%           
=======================================
  Files          57       57           
  Lines        4472     4472           
  Branches      922      922           
=======================================
  Hits         4183     4183           
  Misses        289      289           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mark-wiemer]

Thanks for this! Blocking on me actually taking action to set things up on the npm side, but now is a good time to do so with the v12 betas and whatnot :)

[JoshuaKGoldberg]

I went through https://www.npmjs.com/package/mocha/access and added release-please.yml as a trusted publisher file for mochajs/mocha. 👍