chore: Node.js release key sync

[nodejs-github-bot]

Open based on changes from update-keys.sh. For details on whose key is changing, look at https://github.com/nodejs/node#release-keys

[nschonni]

@aduh95 there was an error when I triggered it around tagging the releasers

Error: Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the nodejs/docker-node repository. - https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request

[aduh95]

I've added the releasers team as triagers on this repo to unblock review requests and codeowners

[MikeMcC399]

LGTM and we now have releasers cross-checking, which is even better 👍🏻

[PeterDaveHello]

Only the order changed?

[MikeMcC399]

Only the order changed?

Correct!

The script update-keys.sh copies the keys in the same order that they are listed in the node > README, where they are sorted in alphabetical order by first name of the signer using the key.

The new key 655F3B5C1FB3FA8D1A0CA6BDE4A7D232B936D2FD for @sxa was manually added at the end of the list, instead of using the original order. This caused the mismatch between manual update and automatic update.

See also issue #2569