Release workflow is broken for patch releases from existing release branches

[eguzki]

Summary

The Release operator
workflow cannot perform patch releases from an existing release branch (e.g. release-0.23).

Bug 1: Wrong OLM replaces directive in patch release bundles

make prepare-release always overwrites the replaces field by fetching the latest GitHub
release, ignoring the value already committed in the release branch's build.yaml. For a patch
release from release-0.23, this produces a bundle with a wrong spec.replaces pointing to a
newer minor release instead of the previous patch.

Bug 2: Direct push to release branch is blocked by the repository ruleset

The workflow pushes the prepared commit directly to the release branch. The org-level ruleset
covers refs/heads/release* and requires a pull request with at least 1 approving review. The
workflow uses the default GITHUB_TOKEN, which has no admin bypass. The push fails.

Fix

Align the release workflow with the pattern used in other Kuadrant repos (e.g.
kuadrant-operator) and document the patch
release process in RELEASE.md.