Onboarding @aduh95 as a releaser

[ruyadorno]

After our meeting session at the Node.js Collaborator Summit at London 2024, @aduh95 reached out to participate in the Releaser Team 🎉

Onboarding actions (from GOVERNANCE.md):

• @aduh95 to prepare a release (promoted by an existing releaser)
• Be added to the GitHub releasers team in the Node.js org (grants ci-release access)
  • Added to backporters team
• Be added to the GitHub security-release team in the Node.js and nodejs-private orgs
• Have a single, high quality SSH key added to the "dist" user on the primary www server
• Have a GPG key added to the nodejs/node README.md
  • The key should be cherry-picked to all active release branches.
  • Open a PR in nodejs/docker-node to add gpg key to node.keys
  • Add the key to https://github.com/nodejs/release-keys

[richardlau]

In today's meeting @aduh95 said that he'd like to prepare another release before becoming a releaser.
I have added him to the backporters team, which will allow him to update the staging branches to help prepare a release.

[richardlau]

@aduh95 I've added you to the releasers and security-release GitHub teams

I've also added your key from https://github.com/aduh95.keys to the primary www server. There's a pinned message to the #nodejs-release-private Slack channel (which I added you to) that details the jump host -- you should be able to ssh into that server as the dist user now. If you'd rather use a separate ssh key, let me know (also for anyone, the reference for generating a ssh key: https://github.com/nodejs/Release/blob/main/GOVERNANCE.md#ssh-key-guidance).

For your gpg key used to sign the release, please could you open the PRs as per the checklist?

[richardlau]

Looks like all the steps have been completed and @aduh95 was able to release Node.js 22.10.0 🎉.