help request: I am unable to deploy APISIX version 3.15 via Helm within a GKE 1.35 cluster.

### Description

GKE version: 1.35.1-gke.1396002
apisix helm chart version: 2.12.6
apisix version: 3.15.0
In GKE version 1.35, a `validatingadmissionpolicy` resource called `enforce-gateway-standard-channel` was added. This prevents the deployment of gateway API-related resources with the `gateway.networking.k8s.io/channel: experimental` annotation. Unfortunately, this annotation is present in the `gwapi-crds.yaml` file within the Apisix charts, causing Helm deployment failures. This is because gateway API-related resources are deployed through GKE's own components. While Apisix's gateway API-related CRD resources don't need to be deployed, I couldn't find a corresponding switch in `values.yaml`. The only solution I can think of is deleting the `gwapi-crds.yaml` file. Are there any better workarounds?

### Environment

GKE version: 1.35.1-gke.1396002
apisix helm chart version: 2.12.6
apisix version: 3.15.0

Start by inspecting gwapi-crds.yaml and values.yaml in the APISIX Helm chart, then reproduce the deployment failure on the stated GKE 1.35.1 environment with chart 2.12.6. Determine whether the Gateway API CRDs can be skipped or configured safely when GKE supplies them; done means a documented or tested workaround that allows Helm deployment without conflicting resources.

Written by the indexing model from the issue text.