Test Details Overview

Rewrite Prepare Release and describe the whole release process

Prepare Release cuts the release branch and moves develop on to the
next major. The job did it in six inline steps: it fetched the default
branch name over the REST API, bumped the major on a timestamped branch,
opened the pull request, hard-reset its checkout and only then created
the release branch, from the default branch whatever ref it had been
started on, with no permissions block and a typo in a step name.

ci/deploy/prepare-release.sh does the same work in the order a reader
expects, refuses to run on anything but the default branch or when that
branch is not at <major>.0, and takes --dry-run like the tag generator.
It shares the version helpers with next-tag.sh through common.sh and
names the pull request's repository explicitly, so a fork never opens
one against the upstream repository.

The README now opens with the release process itself: how development
builds come about, the steps and the order for a release, point
releases, rebuilding a tag, and where the workflows stop.

__________

Type: commit

Hash: 9d9d6502b6be0d692bfa55a32c88e9b1f368d689

Created: yesterday

__________

gr0v1ty/nano-node:9d9d6502b6be0d692bfa55a32c88e9b1f368d689