[EKS] [Request]: Supporting WARM IP feature with SGP (Security Group for Pod)

### 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**
Improvements are needed to prevent EC2 API throttling issues by providing the WARM IP feature like in an environment using ENI Secondary IP (without SGP).

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
If the creation/deletion of a Pod with the SGP function applied is repeated, Pod creation is delayed due to EC2 API throttling. When operating with ENI Secondray IP (without SGP), this problem is bypassed through WARM IP and WARM ENI. But SGP does not yet provide the WARM IP function, so EC2 API Throttling issues cannot be avoided.

**Are you currently working around this issue?**
We are responding temporarily by increasing EC2 API request limit. However, because there is a limit to increasing the EC2 API request limit, the WARM IP function is necessary.

No repository files, tests, or entry points are identified. Start by reviewing EKS VPC-RC, Security Groups for Pods, and the existing WARM IP/WARM ENI behavior; done means providing equivalent WARM IP support for SGP without the reported EC2 API throttling during repeated Pod creation and deletion.

Written by the indexing model from the issue text.