Fix publishing

[jreineckearm]

• Restrict permissions in workflows to what's needed.
• Update CI to fulfill requirements for OIDC (node 22)
• Removed NPM token from workflow and set permission id-token: write to enable OIDC.

Related EF IT helpdesk ticket to set up Trusted Publishing on three packages we maintain and that I am aware of:
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7195 (updated to an issue, was task before)

[cwalther]

Looks sensible at a glance, but I’m not familiar with the process, so I guess we’ll just have to see whether it works, and wait for feedback from the helpdesk.

[jonahgraham]

I don't really know the details here, but I am ok with the experiment.

---

VSCode is on Node 22 these days, so updating to Node 22 is fine by me. But I don't think we should hide it in here and instead make it explicit, for example in the README (this line)

If we stop build & test with node 20, I don't think we should spend too much time trying to support it going forward. Keeping our test matrix as small as possible would be best (and it is already big)

[jreineckearm]

make it explicit, for example in the README

Thanks, forgot about the docs, will update.

[jreineckearm]

Updated cdt-gdb-vscode to node 22 for consistency as part of eclipse-cdt-cloud/cdt-gdb-vscode#200

[jreineckearm]

Trusted publishing has been set up now. It should just work.... (famous last words).
Merging and giving it a try with a 1.7.1 release.