Component nudges is supposed to trigger a new FBC build every time an operator-bundle is published but it seems like it doesn't work.

Similarly, operator-bundle build should be respinning every time there's a new hub or operator build, but that's not working either.

So... we need another process for this.

Could be one of:

• move catalogs/ folder from rhidp/rhdh GL to its own GH repo
• create a GH action to run every n minutes to check for the latest operator-bundle image for a given branch, against a file with a previously-cached image+tag+digest
• if a change is found, update the sync cache file
• run the renderCatalogs.sh script; commit changes
• watch as the Konflux FBC pipelines respin

OR

• create new sync/quay.io_SHA_rhdh-operator and sync/quay.io_SHA_rhdh-hub files, which are tracked by cel expression in the operator-bundle push script:

      pipelinesascode.tekton.dev/on-cel-expression: event == "push" && target_branch
        == "rhdh-1-rhel-9" && ( "distgit/containers/rhdh-operator-bundle/***".pathChanged() ||
        ".tekton/rhdh-operator-bundle-1-push.yaml".pathChanged() )
  

• update that file every time we run sync-midstream.sh
• create a new sync/quay.io_SHA_rhdh-operator-bundle file, which is tracked by cel expression in the fbc push scripts
• as part of sync-midstream, if the quay latest tag + digest has changed, run renderCatalogs.sh + commit changes

In either case, a --commit flag should be added to the renderCatalogs.sh script so it will commit the local changes or generate a PR if it can't push directly.