Prepare release script for patches

[jtoar]

Partially closes #2067. This PR prepares the release script for releasing patches.

Also, you can now pass options to answer some of the questions from the CLI and speed things up:

yarn release --semver minor --no-prs --checkout

But "check" steps will never be skipped.

@thedavidprice, a couple things:

-> I've seen two syntaxes for checking out the release branch:

# 1
git checkout -b release/patch/v0.28.1 v0.28.0
# 2
git checkout tags/v0.28.0 -b release/patch/v0.28.1

I'm going with the first one because that's what's in the git-tagging docs: https://git-scm.com/book/en/v2/Git-Basics-Tagging (at the end—"Checking out Tags").

-> This script now handles updating next-release-patch pull requests.

-> This one's probably obvious but we probably have to do a run through to get this 100% right.

[thedavidprice]

@jtoar I didn't quite follow you here:

-> I've seen two syntaxes for checking out the release branch:

1

git branch release/patch/v0.28.1 v0.28.0

2

git checkout tags/v0.28.0 -b release/patch/v0.28.1

I'm going with the first one because that's what's in the git-tagging docs: https://git-scm.com/book/en/v2/Git-Basics-Tagging (at the end—"Checking out Tags").

You are saying we should try git branch ...

Just looked through the docs and saw this, which implies git checkout ... for me:

I haven't tried git branch ... yet. No preference by me if the results are the same. TBD

[jtoar]

@thedavidprice Sorry, I meant to say checkout instead of branch! Updating the OP now.

[thedavidprice]

@jtoar Ah, that makes sense! Thanks.

[jtoar]

@thedavidprice merging now before we do a run through 'cause I'm sure we'll have to tweak then.

[Thompson1985]

Looks good