Add configs for gatewayAPI cluster deployment

[KashDev00]

Closes https://github.com/isisbusapps/docker-orchestration/issues/1024

Uses Helm to deploy Envoy gateway proxy, which also installs the CRDs.

Creates the Gateway class and gateway, which automatically provisions a load balancer using the existing OCCM integration to direct pod traffic.

Created an HTTP route for the messages service to test on the CAPI cluster and Visits frontend HTTP route on the backup cluster.

Runs in parallel with the existing ingress controller for a gradual migration.

We need to add an HTTPRoute file for all the apps and deploy it.

[ACLay]

Can we add a kustomization.yaml file that references all of the other yaml's so that these configs can be deployed automatically by argocd?

Incase it's useful for the prod migration, I used the following commands to get names of gateway httproutes and ingresses for comparison to figure out what hadn't had gateway config deployed:

kubectl get ingress -n apps | grep -Po "^[^ ]+"
kubectl get httproute -n apps | grep -Po "^[^ ]+"

[ACLay]

Can we also add files so that argocd automatically installs the chart? U&A have a couple examples in their message broker component directories.

[KashDev00]

This is a one-time setup(part of cluster deployment). Also, we will be moving soon to the distributed cluster.

Using Argo CD seems to be a bit dangerous for cluster setup(could allocate multiple FIPs if something were to go wrong, and it tries to sync)