Jordan Harband onboarding

• Be added to the GitHub releasers team in the Node.js org (grants ci-release access)
• 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 (see below for guidelines regarding SSH key quality)
• Open a PR to add their GPG key to the nodejs/node README.md
  • Once landed, the key should be cherry-picked to all active release staging branches (i.e. the active vMM.x-staging branches).
  • Any future updates to the key should also be cherry-picked to all active release staging branches.
• Open a PR in nodejs/docker-node to add their GPG key to node.keys
• Open a PR in nodejs/release-keys to add their GPG key via ./cli.sh add $KEY_ID:
• Open a PR in nodejs/Release to add themself under the "Releasers team" heading via ncu-team sync README.md.
• Add them to the #nodejs-release-private team on the OpenJS Slack.

cc: @ljharb

Start with the checklist and verify the requested access and key changes across the Node.js org, server, README.md, release staging branches, nodejs/docker-node's node.keys, nodejs/release-keys via ./cli.sh add, and nodejs/Release via ncu-team sync README.md. Done means every checklist item is completed, including the OpenJS Slack team addition.