Description of problem:

In HCO, there are two fields:
tektonPipelinesNamespace: test-01
tektonTasksNamespace: test-01
If i enable them then pipelines will get created under test-01 namespace and also all the rbac and rolebindings are set up for test-01. Having configmaps under these custom namespace seems to be more useful and logical because by setting this user intend to use test-01. Currently, they are getting created under openshift-virtualization-os-images.

Version-Release number of selected component (if applicable):
CNV 4.14

How reproducible:
always

Steps to Reproduce:
1.add above mentioned fields in HCO under spec.
2. save and see if test-01 has pipelines created and rbac.
3.

Actual results:
configmaps still created under openshift-virtualization-os-images.

Expected results:
configmaps should be created based on fields tektonPipelinesNamespace and tektonTasksNamespace

Additional info: