Description of problem:

When the Builds operator comes up, it creates a `TektonConfig` instance that deploys Tekton/OpenShift Pipelines on the cluster admin's behalf.

This instance assumes an older version of the TektonConfig, and does not add newly required settings for the pruner (must define either `keep` or `keep-since`).

Workaround: Install OpenShift Pipelines first, then install Builds for OpenShift

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

Builds for OpenShift 1.2.0 (probably 1.1 as well)
OpenShift Pipelines 1.16.1
OpenShift 4.17.4

Steps to Reproduce

1. Install Builds for OpenShift from OperatorHub
2. Check and see if OpenShift Pipelines is deployed properly
    

   Actual results:

OpenShift Pipelines does not deploy properly - a patch/edit needs to be made on the generated TektonConfig. See SRVKP-6832

Expected results:

OpenShift Pipelines deploys correctly.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

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