[eks] [feature]: EKS add-on support for multus

### 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**
Support multus as an EKS add-on, rather than the current apply the manifest method. Improve security by adding additional security related attributes restricting what it can do.

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

**Are you currently working around this issue?**
Using the following terraform to deploy it, and instructing terraform_checkov to skip the file
```
data "kubectl_path_documents" "multus" {
pattern = "./manifests/aws-k8s-multus.yaml" # https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/multus/v3.9.2-eksbuild.1/aws-k8s-multus.yaml
}
resource "kubectl_manifest" "multus_manifests" {
for_each = toset(data.kubectl_path_documents.multus.documents)
yaml_body = each.value
}
```

Start by reviewing the EKS add-on request and the referenced Terraform resources, including the aws-k8s-multus.yaml manifest path. Define what EKS-managed multus support and its additional security restrictions should provide; done means multus is supported as an EKS add-on instead of requiring the current manifest-application workaround.

Written by the indexing model from the issue text.