bug: using gatewayproxy, ingress resource does not update status.loadBalancer.ingress

### Current Behavior

The ingress resource does not update status.loadBalancer.ingress, which will cause the ingress resource status in argocd to be processing。

see

kubernete ingress resource：

argocd ingress status：

### Expected Behavior

kubernete ingress resource：

argocd ingress status：

Cause of the problem：

The gatewayProxy in the apisix ingress controller helm chart does not define a publishService if apisix is ​​deployed in a k8s cluster.

I configured publishService and the problem was restored。

### Error Logs

no

### Steps to Reproduce

1. install apisix ingress controller with the helm chart.
2. use argocd create ingress resource.

### Environment

- APISIX Ingress controller version (run `apisix-ingress-controller version --long`)

2.0.4rc

- Kubernetes cluster version (run `kubectl version`)

1.34

- OS version if running APISIX Ingress controller in a bare-metal environment (run `uname -a`)

Start by inspecting the APISIX Ingress Controller Helm chart's gatewayProxy configuration and how publishService is handled during installation. Reproduce the issue with the listed Helm and Kubernetes steps, then verify that the Ingress status.loadBalancer.ingress is populated and ArgoCD no longer reports the resource as processing.

Written by the indexing model from the issue text.