Migrate to OIDC on publishing npm packages in GitHub Actions

See https://docs.npmjs.com/trusted-publishers for documentations.

[!note]
Trusted publishing requires npm CLI version 11.5.1 or later.

TL;DR: add the following section in the workflow file to replace ${secrets.NPM_TOKEN}, and create OICD connection on https://www.npmjs.com/package/<package-name>/access:

permissions:
  id-token: write  # Required for OIDC
  contents: read

This should help us get rid of npm tokens in GitHub Actions for publishing packages.

Quick search on npm token usages: https://github.com/search?q=org%3Anodejs+path%3A%22.github%2Fworkflows%22+%22npm+publish%22&type=code

• nodejs/node-gyp
• nodejs/undici
• nodejs/corepack
• nodejs/amaro
• nodejs/caritat: https://github.com/nodejs/caritat/pull/86
• nodejs/node-core-test
• nodejs/node-api-headers
• nodejs/nodejs.org
• nodejs/require-in-the-middle
• nodejs/node-core-utils
• nodejs/node-addon-api
• nodejs/import-in-the-middle

Inizia con i file workflow non selezionati elencati nell’issue, in particolare nodejs/node-core-test e nodejs/caritat, e confrontali con le migrazioni selezionate. Verifica prima i requisiti di npm trusted-publisher e le autorizzazioni esistenti dei workflow. L’attività è completata quando i workflow di pubblicazione npm rimanenti non usano più NPM_TOKEN e dispongono della configurazione OIDC richiesta.