Description of problem:
pod tekton-results-postgres-0 is not ready even hours after cluster is deployed
This causes test-kubevirt-cnv-4.14-operator-ocs test to fail, because they check that all system pods to be ready before running.

$ oc get pod tekton-results-postgres-0 -n openshift-pipelinesNAME                        READY   STATUS              RESTARTS   AGEtekton-results-postgres-0   0/1     ContainerCreating   0          14h```

Steps to Reproduce:

1. Provision and deploy a new cluster using the deploy-cnv-4.14-on-rhos-ipi job job setting DEPLOY_CNV=FALSE and DEPLOY_OPENSHIFT_PIPELINES=true
   Example: https://jenkins-csb-cnvqe-main.dno.corp.redhat.com/job/deploy-cnv-4.14-on-rhos-ipi/6315/
2. 2. When the cluster is deployed check pod health:
   ```
   oc get pod tekton-results-postgres-0 -n openshift-pipelines
   ```

 Actual results:
Pod status is "Pending"

NAME                        READY   STATUS    RESTARTS   AGE
tekton-results-postgres-0   0/1     Pending   0          6h49m

Expected results:

pod must exist and be healthy

Proposed solution:
1. Reorder stages in the deployment pipeline, so that OCS is deployed before openshift   pipelines.
2. Change deploy_ocs.sh to make OCS the default storage class, at least optionally, controlled by a job parameter.