docs: Update release guide with new process

This MR proposes a slightly different release process and tidies ordering of the release guide a little.

The process matches what other projects (such as Kubernetes) use, and I think will allow us to better manage releases, especially post-1.0 when we might want to support the last N minor versions.

Comments welcome!