1. Proposed title of this feature request
Expose default-imagepullbackoff-timeout so it can be configured

2. What is the nature and description of the request?
With default-imagepullbackoff-timeout being introduced in Tekton (see https://tekton.dev/docs/pipelines/additional-configs/#taskruns-with-imagepullbackoff-timeout) it's key and required to expose this option in the OpenShift Pipelines offering so it can be configured in environment required.

In many customer environment, it's not uncommon that specific latency between OpenShift Container Platform 4 - Cluster and Image Registry is observed, hence impacting the experience with OpenShift Pipelines. Also Tasks relying on the OpenShift Container Platform 4 - Image Registry may actually fail on newly created OpenShift Container Platform 4 - Node(s) created by the autoscaler because some of the required components may not be ready when the associated task pod is already started on this OpenShift Container Platform 4 - Node.

Having a way to allow some grace during such problems is very much key and will improve the user experience very much as it will avoid failed runs because of unknown reason (unknown for the actual user)

3. Why does the customer need this? (List the business requirements here)
Depending on the Infrastructure environment available at the customer, it may be required to allow the cluster operators to decide whether to wait in case of an imagePullBackOff or to fail. With regards to user experience it's often preferred to wait for some time and therefore configuring default-imagepullbackoff-timeout is very much desired.

4. List any affected packages or components.
OpenShift Pipelines