Description of problem:
After not installing marketplace-operator(https://issues.redhat.com/browse/OLM-2415), the OLM still uses its project as the default catalogsource project.

mac:openshift-tests-private jianzhang$ oc rsh catalog-operator-66b46bcdbd-r6t7w
sh-4.4$ ps -elf|cat
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
4 S 1001 1 0 0 80 0 - 395122 - 06:10 ? 00:00:05 /bin/catalog --namespace openshift-marketplace

Version-Release number of selected component (if applicable):
Cluster version is 4.11.0-0.nightly-2022-04-16-163450

How reproducible:
always

Steps to Reproduce:
1. Set the below flag at the install time to disable the marketplace-operator installation.
baselineCapabilitySet: None

2. Check OLM catalog-operator running flags.

Actual results:
Still use the non-exist 'openshift-marketplace' as the default catalogsource project. This will lead to some limits, such as,
if end user creates the CatalogSource in a project, so the end user has to subscribe to the operator in the same project, otherwise, will get the below errors:

• message: 'constraints not satisfiable: no operators found from catalog community-operators
  in namespace jian referenced by subscription etcd-0.9.4, subscription etcd-0.9.4
  exists'

Expected results:
The OLM doesn't use the non-exist 'openshift-marketplace' project as the default catalogsource project.
Or we should describe the limit in OCP4.11 release doc.

Additional info: