Currently, OLMv1 blocks upgrades when it detects installed operators which have a maxOpenShiftVersion property where the value is the currently-installed OCP clusterversion, with a message that looks like 

Found ClusterExtensions that require upgrades prior to upgrading cluster to version 4.$currentMinor+1

With 5.0 coming, we need to consider the migration paths 4.22 --> 4.23 as well as 4.22 --> 5.0.  We must include specific version information in the message in order to help customers identify specific restrictions.

HOWEVER, we do not yet know if there will be OCP4 releases after 4.23 OR what migration paths will need to be considered, so we want to implement the smallest thing possible which will break earliest/loudest when conditions change, so the decision is to hardcode the message for the 4.22 release. 

Impacted code area:

https://github.com/openshift/cluster-olm-operator/blob/main/pkg/controller/incompatible_operator_controller.go