1. Proposed title of this feature request
Enable customisation of Gateway API versions

2. What is the nature and description of the request?
In recent versions of OpenShift, Gateway API CRDs were introducted and are managed by cluster operators. The Gateway API version is tightly coupled to the OpenShift release version and cannot be customised by the user. To improve flexibility and support of newer API versions the implementation of the ability to customise the Gateway API version is requested, either by:

• allowing the selection of a version/channel of GatewayAPI CRDs managed by the ingress operator
• allow the ability to disable the management of the GatewayAPI CRD by the ingress operator and specifiy a custom/manual handling

3. Why does the customer need this? (List the business requirements here)
To enable the use of a wider range of partner software, such as the Airlock Microgateway, access to newer versions of the GatewayAPI are required