NR-199374 // Release script

[d3caf]

This adds a new release script which can be invoked via npm run release or yarn release. The script will run through a wizard to ensure that all required env vars are set and will target the selected environment for release. It relies on there being a merged PR from release -> main and requires the PR number.

Testing

• npm install in utils
• Have a staging API token handy
• npm run release
• Can test against [DO NOT MERGE] Test new release script #2181 by providing it as the PR number when prompted. The script only uses the PR to determine which files changed and then runs mutations based on local files, so changes may not actually be accurate unless you've pulled the changes from 2181 locally.

TODO

• Test against local NG
• Commit documentation Docs will live in Confluence and be written as a part of another ticket

[aswanson-nr]

LGTM! One straggler file that needs to be removed, but that it should be ready!

[aswanson-nr]

Let's also disable the failing jobs so that they don't create a lot of noise. We can just comment out the follow lines: https://github.com/newrelic/newrelic-quickstarts/blob/release/.github/workflows/pr-merged.yml#L113-L165

[caylahamann]

The only thing is maybe we should mention / document what the github token is used for and if there is any scenario in which you might need it?? just because i got tripped up on that one