[EKS] [request]: Support a coredns addon install with conflicting k8s-app: kube-dns label value

### 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 have coredns installed in an EKS cluster via the [coredns helm chart](https://github.com/coredns/helm/blob/master/charts/coredns). We migrated to the helm chart back when the add-ons had no advance configuration options. Now, we would like to migrate back to the add-on. However, I believe install is blocked even with `resolve_conficts=OVERWRITE` due to the fact that the helm chart sets `k8s-app: coredns` and the addon sets it to `k8s-app: kube-dns`. This label is immutable, so we cannot modify it via helm chart values after the initial installation. If the add-on permitted an override value, I think the add-on could be installed. This is not as simple as podLabels -- the `k8s-app` key-value pair is used in selectors in other resources, e.g. the coredns service object.

Right now, the add-on installation fails ambiguously. See case ID 14108622841 for full context.

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

**Are you currently working around this issue?**
We're not. We're stuck using the coredns helm chart. We _may_ opt to migrate during a downtime.

**Additional context**
Anything else we should know?
[Yeah, exposing the add-on installer logs would be great](https://github.com/aws/containers-roadmap/issues/2185)

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Start by reviewing the linked CoreDNS Helm chart and the EKS add-on installation behavior described in the issue, including how the k8s-app label is used by the CoreDNS service and other selectors. Confirm the conflicting immutable label and define completion as allowing the add-on migration with an override while preserving dependent selectors and producing a clear installation result.

Written by the indexing model from the issue text.