Today we have 100s of places where 1.y is hardcoded in the bash, python, js scripts. Moving to 2.y will require refactoring scripts and in many cases we will need branching logic for 6mo while we continue to support the 1.y releases until they're EOL.

This Feature blocks doing a 2.y release, including updates to:

• pyxis
• konflux-release-data
• rhdh (gitlab)
• rhdh-plugin-catalog (gitlab)

We need to also review assumptions about old content deletion.

• For example in https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/scripts/tagRelease.sh#L986 when branching we will need to potentially keep old prodsec/pyxis/krd content for another 6mo++
• Same for quay cleanup scripts like https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/scripts/deleteTagsFromQuay.sh and https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/ci/weekly-maintenance.sh#L116