OpenShift 4 upgrade blocked by incompatible Gateway API CRDs

Issue

• OpenShift is alerting external Custom Resource Definitions (CRDs) are present that are now managed by OpenShift's Ingress Operator.
• Providing the Administration Acknowledgement as instructed in the console does not allow the upgrade to begin.

• Clusterversion reports Cluster should not be upgraded between minor versions for multiple reasons: AdminAckRequired,GatewayAPICRDsNotCompatible, and the following messages:

  Gateway API CRDs have been detected. OCP fully manages the life-cycle of Gateway API CRDs. External management is unsupported and will be prevented. The cluster administrator is responsible for the safety of existing Gateway API implementations and must acknowledge their responsibilities via the admin gate to proceed with upgrades. See https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/release_notes/ocp-4-19-release-notes#ocp-4-19-networking-gateway-api-crd-lifecycle_release-notes for details. Failure to read and understand the documentation for this and the implications can result in outages and data loss. Kubernetes 1.32 and therefore OpenShift 4.19 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/7112216 for details and instructions.
  

  Cluster operator ingress should not be upgraded between minor versions: Incompatible Gateway API CRDs found: tlsroutes.gateway.networking.k8s.io, referencegrants.gateway.networking.k8s.io, tcproutes.gateway.networking.k8s.io, gateways.gateway.networking.k8s.io, gatewayclasses.gateway.networking.k8s.io, grpcroutes.gateway.networking.k8s.io, httproutes.gateway.networking.k8s.io, udproutes.gateway.networking.k8s.io
  
  See the release notes for more information: https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/release_notes/ocp-4-19-release-notes#ocp-4-19-networking-gateway-api-crd-lifecycle_release-notes