EKS Addon Creation fails with error " Addon specified is not supported " via cft

### 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**
Trying to Creating Addons for EKS Cluster v1.18 but stack fails

**Which service(s) is this request for?**
This could be EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Trying to Creating Addons for EKS Cluster v1.18 but stack fails with below error

**_Resource handler returned message: "Addon specified is not supported (Service: Eks, Status Code: 400, Request ID: 683c7d50-b441-4c44-b327-fde57c61b150, Extended Request ID: null)" (RequestToken: f5b1072c-8566-9900-e37b-8df89074e6a5, HandlerErrorCode: InvalidRequest)_**

I'm trying to create addon for an existing cluster. Please let me know if I'm missing something below:
My cft template

Resources:
EKSKubeproxyAddon:
Type: AWS::EKS::Addon
Properties:
AddonName: kube-proxy
AddonVersion: 1.18.8-eksbuild.1
ClusterName: !Ref ClusterName
ResolveConflicts: OVERWRITE

CoreDNS:
Type: AWS::EKS::Addon
Properties:
AddonName: coredns
AddonVersion: 1.8.0-eksbuild.1
ClusterName: !Ref ClusterName
ResolveConflicts: OVERWRITE

**Are you currently working around this issue?**
Solving by creating addon via awscli or aws console

**Additional context**
Anything else we should know?

**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 with the reported AWS::EKS::Addon resources in the CloudFormation template and compare the failing stack operation with the AWS CLI or console workaround. Verify the EKS 1.18 cluster and addon versions against the supported combinations; done means both addons can be created through CloudFormation without the reported error.

Written by the indexing model from the issue text.