[aws-load-balancer-controller] Duplicate globalaccelerators.aga.k8s.aws CRD definitions

**Describe the bug**
Both [crds.yaml](https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller/crds/crds.yaml#L193) and [aga-crds.yaml](https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller/crds/aga-crds.yaml#L7) define the `globalaccelerators.aga.k8s.aws` CRD. Since both are included in [kustomization.yaml](https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller/crds/kustomization.yaml), applying results in the error: `may not add resource with an already registered id`.

**Steps to reproduce**
```
kubectl apply -k "https://github.com/aws/eks-charts/stable/aws-load-balancer-controller/crds?ref=master" --dry-run=client
error: accumulating resources: accumulation err='merging resources from 'aga-crds.yaml': may not add resource with an already registered id: CustomResourceDefinition.v1.apiextensions.k8s.io/globalaccelerators.aga.k8s.aws.[noNs]': must build at directory: '/private/var/folders/0c/4vxshjcd38g450vm4drsh2kw0000gp/T/kustomize-2865117982/stable/aws-load-balancer-controller/crds/aga-crds.yaml': file is not directory
```

**Expected outcome**
`kustomization.yaml` should apply successfully.

**Environment**

* Chart name: aws-load-balancer-controller
* Chart version: 1.17.0
* Kubernetes version: 1.32
* Using EKS (yes/no), if so version? yes, 1.32

**Additional Context**:

Start by comparing the duplicate globalaccelerators.aga.k8s.aws definitions in crds/crds.yaml and crds/aga-crds.yaml, then inspect crds/kustomization.yaml to see how both are included. Run the reported kubectl apply -k command with --dry-run=client; done means the kustomization applies without the duplicate-resource error.

Written by the indexing model from the issue text.