Task:
Check if the Istio version was bumped with the new OSSM 2.x version. If yes, check, if Gateway API CRD's version also needs to be updated in the pipeline here: https://gitlab.cee.redhat.com/istio/servicemesh-qe/jenkins-csb-declaration/-/blob/master/jenkinsfiles/install-jobs/install-service-mesh.jenkinsfile?ref_type=heads#L61  ( if not, add new OSSM version into the existing `if` clause ) .
The version of the GatewayAPI CRD's for a particular Istio version can be found here:

https://istio.io/<ISTIO VERSION>/docs/tasks/traffic-management/ingress/gateway-api/

The GatewayAPI needs to be also updated in maistra-test-tool, e.g.  https://github.com/maistra/maistra-test-tool/pull/649

Original description:
Update Gateway API CRD version in install-service-mesh pipeline in order to support OSSM 2.5

Without it, the installation of OSSM 2.5 with Gateway API failed. ( since the pipeline uses old version 0.5.1 https://gitlab.cee.redhat.com/istio/servicemesh-qe/jenkins-csb-declaration/-/blob/master/jenkinsfiles/install-jobs/install-service-mesh.jenkinsfile?ref_type=heads#L57 )

More info: https://redhat-internal.slack.com/archives/C04KW747ZLK/p1702985257996939

Bumping the version to 0.6.2 is not enough because backward compatibility is not guaranteed since the CRDs were in an experimental phase in that version.
So the pipeline must be complex, e.g. e.g. before OSSM is installed, the Gateway API CRDs need to be deleted from the cluster to install the correct one according to the OSSM version.