Kubernetes Gateway API; addition of Ingress replacement objects to XNAT helm chart

[dean-taylor]

Kubernetes is planning on deprecating the Ingress API and migrating to the Gateway API for more control and standardisation of networking interconnects.

The XNAT helm chart requires the addition of these components to comply with fast approaching alterations to Kubernetes deployments.

NB: The experimental Gateway API includes operations for East-West traffic and is already compliant with Istio service mesh.

[dean-taylor]

Do we make this change part of the current release candidate to move to major release 2.0.0?