ArgoCD workflows - make dev and ops flexible when prod is running

[tolzhabayev]

We need to figure out a way to keep the catalogs in dev, ops and prod in sync but without triggering (or making it optional) argocd workflow changes to dev and ops when prod is being released. Mostly because dev and ops might be further ahead already and triggering argocd workflows will effectively roll them "back" to the prod state.

Some context in slack:

• https://raintank-corp.slack.com/archives/C01C4K8DETW/p1755243163955319
• https://raintank-corp.slack.com/archives/C01C4K8DETW/p1756273725766969

We can either go the way of

• opt-in for the argocd workflows to run on dev and ops when prod is triggered when specified explicitly as an input or
• opt-out - making the dev and ops run always and have an input to exclude either both or one of them (list)

[tolzhabayev]

fyi @xnyo if you have any preference for opt-in / opt-out or other thoughts

[svennergr]

Sharing another automated PR that needed manual changes due to this: https://github.com/grafana/deployment_tools/pull/400165