Enabling basic-auth annotation in Higress 2.0+ causes gateway failure with "unable to create wasm http filter basic-auth"

[zijiren233]

Ⅰ. Issue Description

When upgrading to Higress 2.0 or higher, if any Ingress resource has the nginx.ingress.kubernetes.io/auth-type: basic annotation enabled, the Gateway fails to update its listeners. This results in the error unable to create wasm http filter basic-auth, rendering the gateway unavailable and impacting multi-tenant availability in production environments.

---

Ⅱ. Describe what happened

After enabling the nginx.ingress.kubernetes.io/auth-type: basic annotation on an Ingress resource in Higress 2.0+, the Gateway controller crashes or enters a degraded state. The following error is observed in the controller logs:

unable to update/create wasm http filter basic-auth

---

Ⅲ. Describe what you expected to happen

ignore basic-auth config

---

Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. Deploy Higress 2.0+ in a Kubernetes cluster.
2. Create an Ingress resource with the following annotation:

   annotations:
     "nginx.ingress.kubernetes.io/auth-type": "basic"

3. Apply the configuration via kubectl apply -f ingress.yaml.
4. Observe the Gateway controller logs for the error unable to create wasm http filter basic-auth.
5. Verify that the Gateway status becomes unhealthy and new listener updates are blocked.