Bug Description

Since the operator bundle is installed in "all namespaces" mode, OCO is running on the openshift-operators namespace.
If the user clicks create OperatorPipeline from here, the default namespace for this CR is openshift-operators too.
Form View UI doesn't allow changing that. only yaml view does.
It's easy to make the mistake here and proceed to create all tasks and pipelines in operators namespace, while the secrets and configs are in oco NS per documentation.

putting explicitly

namespace: oco

in the sample resource of CSV, should resolve this.