AWS build of Cilium for EKS Anywhere v0.24+

With EKS Anywhere v0.24, EKS Anywhere now installs an AWS build of Cilium with all the features of open source Cilium as the default Kubernetes CNI plugin. Previous versions of EKS Anywhere included a Cilium build with a limited set of features compared to open source Cilium. With this update, AWS will continue to provide technical support for Networking Routing (CNI), Identity-Based Network Policy (Labels, CIDR), and Load-Balancing (L3/L4) capabilities of Cilium with licensed EKS Anywhere clusters, but you no longer need to replace the default EKS Anywhere CNI to use other capabilities available with open source Cilium. For further detail on Cilium features supported by AWS, review the [EKS Anywhere documentation](https://anywhere.eks.amazonaws.com/docs/clustermgmt/networking/networking-and-security/). If you plan to use Cilium functionality outside the scope of AWS support, we recommend obtaining alternative commercial support for Cilium or have the in-house expertise to troubleshoot and contribute fixes to the Cilium project. If you use the default CNI plugin with earlier EKS Anywhere versions and don’t have skipUpgrade set to true, upon upgrading to EKS Anywhere v0.24, the AWS build of open source Cilium will deploy to your cluster with no operational impact. For additional installation instruction and information on migrating from a custom CNI to the new AWS build of Cilium, reference the [EKS Anywhere documentation](https://anywhere.eks.amazonaws.com/docs/clustermgmt/networking/cilium-aws-supported/).

Start with the EKS Anywhere documentation links in the issue, particularly the networking and AWS-supported Cilium pages. The issue names no repository file, test, entry point, or concrete acceptance criteria, so confirm the intended change and define what done means before coding.

Written by the indexing model from the issue text.