[EKS] [request]: being able to add annotations on coredns deployment

### 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**
We want to be able to handle annotations at deployment level, not only on pods.

**Which service(s) is this request for?**
EKS, addon CoreDNS.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
It would help us to tell reloader to rollout coredns once its configmap is updated.

**Are you currently working around this issue?**
We could solve this problem using kyverno but it forces us to remove kube-system namespace from filtered namespace which could involve some unexpected side effect.

**Additional context**
N/A

The request targets the EKS CoreDNS addon and its deployment-level annotations; start by reviewing how the CoreDNS addon deployment and configuration updates are managed. Done means supporting the requested annotations so a ConfigMap update can trigger a CoreDNS rollout without the Kyverno workaround.

Written by the indexing model from the issue text.