[EKS] [request]: auto-deploy of manifests on launch

### 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**
The ability to auto-deploy manifests on creation of the control plane in a similar fashion to how k3s does (see https://rancher.com/docs/k3s/latest/en/advanced/#auto-deploying-manifests).

**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?**

Use Case 1:
> Launching a cluster with changes made to [amazon-vpc-cni-k8s](https://github.com/aws/amazon-vpc-cni-k8s) (e.g. when setting up max warm IP or using custom networking) currently requires either making the appropriate changes before launching any worker nodes or making the changes and then cycling all worker nodes so they follow the new behaviour.

Use Case 2:
> Bringing up a cluster with a set of default system applications so the cluster is in a ready-to-go state. This could include things like log collectors and ingress controllers.

**Are you currently working around this issue?**
Creating the control plane and workers as two different steps with the manifests being applied between.

**Additional context**
N/A

**Attachments**
N/A

Review the EKS control-plane launch flow, including when the control plane and worker nodes become available, and compare it with k3s auto-deploying manifests. Use the amazon-vpc-cni-k8s use case and the requested default system applications to define what must be supported and when deployment is considered complete.

Written by the indexing model from the issue text.