The CVO will pre-create the ClusterOperators to support must-gather, where the concern was:

1. CVO creates a namespace for an operator
2. CVO creates ... for the operator
3. CVO creates the operator Deployment
4. Operator deployment never comes up, for whatever reason
5. Customer must-gathers
5. Must gather uses ClusterOperators for discovering important stuff, and because the ClusterOperator doesn't exist yet, we get no data about why the deployment didn't come up.

With ClusterOperator pre-creation, that becomes:

1. CVO pre-creates ClusterOperator for an operator
2. CVO creates the namespace for an operator
3. CVO creates ... for the operator
4. CVO creates the operator Deployment
5. Operator deployment never comes up, for whatever reason
6. Customer must-gathers
7. Must gather uses ClusterOperators for discovering important stuff, and finds the one the CVO had pre-created with hard-coded relatedObjects, gathers stuff from the referenced operator namespace, and allows us to trouble-shoot the issue

To benefit from that, ClusterOperator manifests should hard-code enough relatedObjects to get a useful gather, but today the cloud-controller-manage ClusterOperator manifest does not set this property.