[EKS] [request]: Apply Tags to EKS created security 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**
When an EKS cluster is created, a security group is created for the control plane (the one with this description: "EKS created security group applied to ENI that is attached to EKS Control Plane master nodes, as well as any managed workloads."). This SG has some tags created by AWS, but additional tags cannot be specific as part of cluster creation.

I'm proposing that tags on the EKS resource itself are propagated to the AWS-created SG; _or_ that a mechanism is provided to specify tags for the SG at creation (via the console and via API).

**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?**
Many organizations require compliance tags for all AWS resources. While it is possible to separately tag the SG after creation, it's not ideal for automation workflows. It would be must easier if the EKS cluster tags were propagated to the SG at creation.

**Are you currently working around this issue?**
Not using a workaround. A possible workaround is to add the tags to the SG post-creation. We use pure terraform for infra automation and do not want to call out to shell commands to perform tagging.

While it's not a huge burden to perform the tagging post-creation, it would be very convenient if this could be avoided.

No repository files, tests, or entry points are mentioned; begin by reviewing EKS cluster and control-plane security-group tagging behavior and the stated Terraform automation constraint. Done would mean a supported way to apply requested tags to the AWS-created security group at cluster creation, either through cluster tags or explicit security-group tag configuration.

Written by the indexing model from the issue text.