Per this discussion..

• https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1717627643868409
• https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1718264631100749?thread_ts=1718218230.029599&cid=C04CUSD4JSG
• https://docs.google.com/document/d/1ImUz5NjtDM01laIhGI6eHSe07hpdWEtYI4EL9GGsgKg/edit#heading=h.6uihbzfopef1

it's been suggested we want to encourage users to be on a y-stream channel as the default as it's safer for 6mo (and then requires manual effort to move to the 1.y+1 or 1.y+2 channel when the 1.y version is EOL).

I'm not sure I agree with encouraging people to get "stuck" on maintenance versions, but that's the idea.

Today we default to the fast channel:

• https://github.com/janus-idp/operator/blob/main/.rhdh/bundle/metadata/annotations.yaml#L6 (could set new default every time we branch for a new stable 1.y release)

• https://github.com/janus-idp/operator/blob/main/.rhdh/scripts/install-rhdh-catalog-source.sh#L27 (would require passing in a channel or product stream version (1.1, 1.2) as we can no longer just do `fast`)

Definition of done:

• set new default
• build container downstream
• validate it works
• communicate change to QE and verify this is reflected in their e2e testing defaults
• check if the install guide mentions `fast` or `fast-1.y` as the default and if necessary submit a PR for the change