Provide a way to remove/install without kube-proxy

**What would you like to be added**:
We would like to be able to remove the kube-proxy (OR install cluster without it at the first place) in a way how EKS-A will not reinstall/try to manage it so, we can use Cilium community in a kube-proxy replacement mode.

**Why is this needed**:
Due to several limitations/missing features in the bundled Cilium, we are replacing it with the community version of Cilium. We would like to start to use the community [Cilium's Gateway API implementation](https://docs.cilium.io/en/stable/network/servicemesh/gateway-api/gateway-api/#gs-gateway-api) for ingress. This requires Cilium to be in [kube-proxy replacement](https://docs.cilium.io/en/stable/network/kubernetes/kubeproxy-free/#kubeproxy-free) mode.
That in turn requires us to remove the kube-proxy daemonset from the nodes after installation so, Cilium can replace it with it's own solution.

We may be able to remove the daemonset already (`kubectl -n kube-system delete ds kube-proxy`) but I guess EKS-A should be aware of this so, it will not try to reinstall it during an upgrade (or while using gitops).

Start by investigating how EKS-A installs and reconciles the kube-proxy daemonset during initial cluster setup, upgrades, and GitOps use. Compare this with the reported `kubectl -n kube-system delete ds kube-proxy` workflow; done should allow community Cilium to provide kube-proxy replacement without EKS-A reinstalling or managing kube-proxy.

Written by the indexing model from the issue text.