[EKS] [request]: Support more than 5 security groups in one CRD for VPC RC

### 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**
What do you want us to build?
We would like to be able to use Security Group names when leveraging SG for Pods functionality.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

According to "Amazon VPC Quotas," it should be able to use up to 16. One CRD must support at least 10 security groups
If I need more than 5 security groups, it's hard to manage
because I need more than one crd. I don't know why one crd doesn't support more than 10 security groups

**Are you currently working around this issue?**
How are you currently solving this problem?
- We forked VPC Resource controller

**Additional context**
Anything else we should know?

https://github.com/aws/amazon-vpc-resource-controller-k8s/pull/413

Start by reviewing the EKS VPC Resource Controller context and the related pull request #413. Compare the current CRD security-group limit with Amazon VPC Quotas and clarify whether the requirement is more than 5 or at least 10 groups. Done means the agreed number of security groups can be managed through one CRD without the reported workaround.

Written by the indexing model from the issue text.