[EKS] [Request/Question]: Make AmazonEKSEditPolicy able to edit any ressources (Kubernetes API Group : *)

### 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

**Tell us about your request**
I recently tried the EKS Access Entry policies. In particular that one : `arn:aws:eks::aws:cluster-access-policy/AmazonEKSEditPolicy`. And got an issue, when I tried to create ressource from a CDR.

The issue itself makes sense : Create action are only allowed for a given set of api (Cf the [doc](https://docs.aws.amazon.com/eks/latest/userguide/access-policies.html), and my CDR is not within. Ok.

But here is the question : Why do not allow such behavior?
And here is the request : Allow such behavior :D

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
My case is quite simple : I want to allow my CI role to deploy some home-made helm chart. The chart create this ressource : `ciliumnetworkpolicies.cilium.io` (For instance, allowing traffic between pods from the same namespace), which is blocked

**Are you currently working around this issue?**
I will either by-pass the issue by using the ConfigMap authentication mode, or assign a kubernetes_group with the correct permission to my access entry. I don't have tested it yet

**Additional context**
This is somewhat related to that [feature request](https://github.com/aws/containers-roadmap/issues/2411) (As it would allow me to define my own policy, solving my issue)

Start by reading the linked Amazon EKS access-policies documentation and compare AmazonEKSEditPolicy's allowed API groups with the CiliumNetworkPolicy resource described here. Review the related feature request in issue 2411; the work would be complete when the policy can support the requested custom-resource deployment behavior or its intended policy configuration is clearly defined.

Written by the indexing model from the issue text.