* Refactor GitHub release workflows
Refactor GitHub release workflows in order to comply with branch protection
rules. The new process:
1. Run the "Create new release PR" manually, selecting the release type
("major", "minor", or "patch"). This will create a new branch
including the Changelog update and the version bumo on the readme,
create-block-theme.php, and package.json files.
2. Merging the PR created on the previous step will trigger the deploy
workflow, which remains unchanged, except for the conditions added in
order for it to run only if the merged PR matches the characteristics of
automated release PR.
1. Fork this repo
2. Checkout this branch
3. Merge intro trunk on the fork
4. Run the workflow, a new PR should be created on the fork
5. Merge the PR; the automated deploy step will run. At this point, the
only thing that you'll be able to test on the fork is that the deploy
workflow correctly identifies the PR and branch as a new release. The
deploy itself requires credentials only available on the parent repo.
* add block themers as reviewers
* prefix tag with v
* add block themers as reviewers
* move version prefix to step where it's needed
* add deploy step name
* add trailing backslash
* remove reviewer
* add block-themers as reviewers for the release pr
* Run google fonts update on release, automerge
* add missing & line end
* add --squash to pr merge
* split update and commit
* Uncomment repo check
It was commented out for testing on a fork.
* Remove date print on workflow log
