Automate Node.js PR for npm Releases

[darcyclarke]

Problem statement

Currently our process for opening a pull requests against the Node.js Project is almost entirely manually done post-release; Letting computers do the work here will save developer time & mindshare as well as reduce complexity or potential for human error.

Features

• a GitHub Action kicks off & generates a pull request for npm cli releases
• a GitHub Action to manually generates a pull request for npm cli releases
• targets the correct branch in the upstream node repo (ie. node:master)
• the correct PR title & description are generated from the release/changelog (ex. https://github.com/nodejs/node/pulls?q=is%3Apr+is%3Aclosed+npm+label%3Anpm)
• should support creating PR's against the correct branches using npm versions (manual overrides are possible w/ GitHub Action inputs)
• the GitHub Action should live inside npm/cli

Exit criteria

• add @gimli01 to the npm team inside the nodejs/node project (@darcyclarke)
• ensure a GitHub/npm bot us responsible for the PR created
• release process/documentation is updated
• feature-set fully implemented/functioning
• Node.js Release WG is made aware of the changes to our process

Useful Links

• Release WG
• Our Current Release Process
• Node.js Maintaining npm Guide

Meeting with @ruyadorno

• ask for branch mappings from cli to nodejs for support branches