disable pruning temporarily, work around weird operator validation error

after fixing the pruner config typo, using disabled instead of disable,
kept getting this inexplicable error in the operator validating webhook,
even though only 'keep-since' was used and not 'keep'

`validation failed: expected exactly one, got both: spec.pruner.keep, spec.pruner.keep-since,Reason:BadRequest,Details:nil,Code:400,`

rh-pre-commit.version: 2.3.1
rh-pre-commit.check-secrets: ENABLED

Author: gabemontero

operator/gitops/argocd/pipeline-service/openshift-pipelines/tekton-config.yaml

@@ -190,12 +190,4 @@ spec:
       kube-api-qps: 50
       kube-api-burst: 50
   pruner:
-    # The load on prod-rh01 is to the point now where tekton-results
-    # can fall too far behind.  Until the watcher's log storage is rewritten
-    # etc with SRVKP-4347 or if we risk adding more processing power (threads,qps,burst)
-    # to the mem leak version of the watcher, we need the OSP pruner as a backup.
-    disable: false
-    keep-since: 60
-    resources:
-      - pipelinerun
-    schedule: "*/10 * * * *"
+    disabled: true