Description of problem:

When setting targetNamespace to openshift-operators leads to some possible very weird behavior for other operators that are installed here.

See https://issues.redhat.com/browse/ROX-15440?focusedCommentId=21836652&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21836652

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

• Install the operator
• Update tektonconfig to set the targetNamespace to openshift-operators

Actual results:

It is allowed, and it might break other operators or upgrades.

Expected results:

It is disallowed.

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Additional info (Such as Logs, Screenshots, etc):

We should just update the tektonconfig_validation.go and disallow a set of hardcoded namespaces (like openshift-operators)