Describe the release process the repository actually has !3

RELEASING.org described a GitHub-native repository. origin is gitbay, and the release only works because gitbay push-mirrors to github.com/krazywarez/orgo, tags included — a fact the document never mentioned and the whole process depends on.

• Where the repository lives is now the first section: origin, the mirror, what the mirror triggers (release.yml on a tag, docs.yml on a push to main), and that neither forge runs the tests — ci.yml was removed and there is no .gitbay/ci.yml, so the pre-flight checks are the only gate.
• Two missing steps. The build checks the tag against Cargo.toml rather than trusting the two to match, and releasing on gitbay needs the notes and binaries by hand.
• gh run list -R krazywarez/orgo is how you watch a release, since gh talks to the mirror.
• repository in Cargo.toml pointed at the mirror rather than at the repository, as did the git clone line in the README and the install guide. Verified that git clone https://gitbay.org/krz/orgo works over HTTPS.
• Two comments claimed CI checks the MSRV on every change. Nothing checks it now.

The repository change reaches crates.io with the next release; 0.23.0 is already published pointing at the mirror.