[EKS] [request]: Add AWS Node termination Handler as an Add-On

### 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?
Create an EKS addon for https://github.com/aws/aws-node-termination-handler

**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?**
The Node Termination Handler is being installed manually on the EKS clusters. As of June 25th, 2021 the only add ones are VPC CNI, CoreDNS, and Kube-proxy.

It'd be great if we didn't have to manually install the node termination handler.

**Are you currently working around this issue?**
Yes we are manually installing the add on.

**Additional context**
N/A

**Attachments**
N/A

Start by reviewing the upstream aws-node-termination-handler project linked in the request and comparing it with the existing EKS add-ons named here: VPC CNI, CoreDNS, and kube-proxy. Define what EKS add-on support would require and consider the manual-install workaround resolved only when the handler is available through EKS add-ons.

Written by the indexing model from the issue text.