Check and update the tekton pruner cronjob

[tbaker1313]

Describe the issue There's a problem in all clusters regarding a tekton pruner cronjob that should be working in the namespace openshift-pipelines, but instead it's present and trying to run in the openshift-operators namespace. To fix this, deleting the tekton pruner cronjob in openshift-operators appears to fix the issue.

Additional context Red Hat case 03618807

How does this benefit the users of our platform? Ensures the tekton pipelines are properly pruned.

Definition of done

• [x] fixed in CLAB
• [x] fixed in KLAB ~- [ ] fixed in KLAB2~
• [x] fixed in SILVER
• [x] fixed in GOLD ~- [ ] fixed in GOLDDR~ ~- [ ] fixed in EMERALD~

[tbaker1313]

This should be fixed. Will check tomorrow after the cronjob runs this evening.

[tbaker1313]

Completed.