Complete RFC 0020 two-phase release workflow rollout across all repos

[thomasmaas]

Summary

RFC 0020 (architecture#178) introduces a two-phase release workflow that replaces the current single-workflow model. Implementation PRs are open in several repos but none are merged yet. This issue tracks completing the rollout across all component repos.

The v1.5.1 release exposed the cost of the current process: the operator image was built with wasm-shim:latest instead of the pinned v0.14.1 because version propagation relies on bespoke shell scripts and Makefile variables rather than a single source of truth. RFC 0020 eliminates this class of bug entirely.

Implementation PRs (open)

• architecture (RFC): RFC 0020: Two-Phase Release Workflow architecture#178
• wasm-shim: Enforce RFC 0020 two-phase release workflow wasm-shim#390
• authorino: Add two-phase release workflow authorino#634
• limitador: Add two-phase release process with automated workflows limitador#494
• dns-operator: Replace release workflows with two-phase release process dns-operator#788
• sector: https://github.com/Kuadrant/sector/pull/91
• helm-charts: Implement RFC 0020: PR-based chart sync workflows helm-charts#41

Repos still needing PRs

• kuadrant-operator
• authorino-operator
• limitador-operator
• console-plugin
• developer-portal-controller
• mcp-gateway

References

• RFC 0020: RFC 0020: Two-Phase Release Workflow architecture#178
• Reference implementation: https://github.com/kuadrant-labs/workflow_layout
• RFC 0018 (branch naming): https://github.com/Kuadrant/architecture/blob/main/rfcs/0018-release-branch-naming.md