Make Clair DB connection string configurable when deployed via the Operator

What problem/issue/behavior are you having trouble with? What do you expect to see?
We want to have a Geo-Replication deployment using the Quay Operator. Quay database and storage can be configured to point to share one but Clair database cannot be configured to point outside OCP, the Clair configuration is hardcoded and is pointing to PostgreSQL running in OCP.

To solve this we have to manually deploy Clair next to the Quay registry, without being managed by the Quay operator.

We need a supported procedure for deployment and upgrade for Clair using a managed database service provided by Azure.

Where are you experiencing the behavior? What environment?
OpenShift 4.7, Quay Operator 3.5.2

What information can you provide around timeframes and the business impact?
This is a blocker, business impact very high