Red Hat OpenShift Pipelines operator upgrade to 1.23 fails because TektonConfig spec.scheduler.disabled is null and the new CRD schema requires a boolean value in RHOCP4

Issue

When upgrading the Red Hat OpenShift Pipelines Operator to version 1.23, the Operator Lifecycle Manager attempts to apply the new TektonConfig CustomResourceDefinition. During this process, the InstallPlan remains stuck in the Installing state and continuously retries or eventually fails with an error indicating that the existing custom resources fail validation against the new CRD schema. Specifically, the logs show the error:

retrying execution due to error: error validating existing CRs against new CRD's schema for "tektonconfigs.operator.tekton.dev": error validating operator.tekton.dev/v1alpha1, Kind=TektonConfig "config": updated validation is too restrictive: [].spec.scheduler.disabled: Invalid value: "null": spec.scheduler.disabled in body must be of type boolean: "null"

Furthermore, attempting to manually edit or patch the TektonConfig resource named config may also fail with errors reporting that the mutating webhook configuration or the validating webhook configuration for the operator cannot be reached.