[EKS] [request]: enable endpoint_pod_names in CoreDNS

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

I think CoreDNS `endpoint_pod_names` should be used so that the DNS records created for pods aren't of the form `...svc.cluster.local` but of the form `...svc.cluster.local` which is much more useful.

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

This request concerns EKS.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

https://kubernetes.io/blog/2018/07/10/coredns-ga-for-kubernetes-cluster-dns/#endpoint-names-based-on-pod-names

**Are you currently working around this issue?**

The `endpoint_pod_names` option has to be applied manually on each newly deployed cluster.

**Additional informations**

While the workaround is quite simple, it's annoying and I haven't found a good reason not to turn on the `endpoint_pod_names` option by default (is there?).

Start with the Kubernetes CoreDNS endpoint-names documentation linked in the issue and investigate how EKS configures CoreDNS. No repository file, test, or entry point is named, so the implementation location must be established first. Done means EKS enables endpoint_pod_names by default, producing pod-name-based DNS records without manual cluster changes.

Written by the indexing model from the issue text.