right now the catalog is located side-by-side with each operator. 

However, we realized this is probably not good because, on the one hand the operator repos will need multiple branches (one branch per release stream), while on the other there is only a need for a single branch in the catalog repo (all 3scale and openshift versions are already in folders and files there)

To Do: 

• move https://github.com/rh-api-management/rh-3scale/tree/main/rh-apicast-operator/catalog to new git repo , maintaining git history
• move https://github.com/rh-api-management/3scale-operator-product-build/tree/main/catalog to same git repo as above, maintaining git history.
• re-create File-Based Catalog component(s) for each operator and OpenShift Container Platform (OCP) version, this time pointing to above git repo (and not rh-3scale / 3scale-operator-build)
• delete old fbc components

Open questions: 

• should we have one FBC component for each operator, or just one for both ?