We would like to deprecate all the EUS channels from OCP catalogs that are not intended for this channel. For example, eus-4.12 should only exist in OCP 4.12 catalog and should not be available in any other OCP version.

Following https://docs.google.com/document/d/19OkfaGgep0bqk7uP3bZ54BNvZJg8JtPVf_vueK2E0TI/edit?tab=t.4qrco0in734u#heading=h.39dtyqywtuu8 we don’t want to deprecate old channels if they are for supported OCP versions, e.g., 4.18-eus channel on OCP 4.14. It is important to still allow their usage, although they were wrongly released as SNR v0.10.1 from the 4.18-eus channel on OCP 4.14.
But for old non-supported `4.12-eus` we should try to deprecate them

Relevant links

• https://github.com/openshift/sandboxed-containers-operator/pull/655/files#diff-a7d9975426ee036565a19f3c6d9defd6fa47223a338075fa7ca1f9c4f8a2d55b 
• Channel naming conventions - https://olm.operatorframework.io/docs/best-practices/channel-naming/#naming 
• Methods for Specifying Updates (Replaces, Skips, and SkipRange)
   - https://olm.operatorframework.io/docs/concepts/olm-architecture/operator-catalog/creating-an-update-graph/#methods-for-specifying-updates 
• Testing an Operator upgrade on Operator Lifecycle Manager - https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/operators/developing-operators#osdk-bundle-upgrade-olm_osdk-working-bundle-images
•