Enhance gateway status to use the Kube api to check the upstream and to include the assigned IP

**Background:**

Some data planes may be on Openshift clusters that use VMware NSX Advanced Load Balancer (AVI Kubernetes Operator), which is an advanced ingress controller. In this case, the `kube-api` will provision an Openshift Route and an IP address will be dynamically assigned. We want the IP address to be available when a user calls the `/v2/namespaces//services` endpoint.

**A/C:**

- move the status logic from `gatewayApi` to `kubeApi`
- have the `gatewayApi` call the `kubeApi` to get the status data
- update the `kubeApi` to enrich the status data with the IP address if it is available

**Technical notes:**

IP address can be found in the Route detail, if the AVI operator is used on the cluster:

```yaml
status:
ingress:
- host: .api.gov.bc.ca
routerName: ako-OCPEMERALD
conditions:
- type: Admitted
status: 'True'
message: 10.99.10.8
```

Start by locating the gatewayApi and kubeApi status logic and the /v2/namespaces//services endpoint. Trace how gatewayApi currently obtains status, then verify the kubeApi can inspect the OpenShift Route detail and expose an available IP. Done means status logic is owned by kubeApi, gatewayApi delegates to it, and the endpoint includes the assigned IP when present.

Written by the indexing model from the issue text.