[EKS] [request]: Application/DNS network policy support for standard EKS clusters

### Summary

Enable Application Network Policies (ANP) support for self-managed Amazon EKS clusters, not just EKS Auto Mode.

### Problem

Amazon EKS recently introduced `Application Network Policies` that allow configuring DNS/FQDN-based egress.

However, this feature is only available for EKS auto-mode clusters. Standard EKS clusters are still limited to L3/L4 Kubernetes NetworkPolicy.

This leads to:

- overly permissive CIDR allowlists when using standard Kubernetes NetworkPolicy.
- forces to use and maintain external CNI components to implement DNS/FQDN-based policies.

Proposal

Extend ANP support to standard EKS clusters.

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

Start by reviewing the issue proposal and the scope of Application Network Policies for standard EKS clusters, then compare it with the stated Auto Mode limitation. Clarify the supported cluster configurations, required AWS or Kubernetes changes, and acceptance criteria with maintainers; done means the roadmap request has an agreed implementation scope.

Written by the indexing model from the issue text.