[EKS] [request]: Allow option/placeholder to manage automatic updates for AWS EKS Addons

### 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 want to be able to manage the updates of `EKS Addons` automatically as per my EKS cluster version updates. For example, if I am using EKS Addons on my EKS `v1.19.x` and updated it to `v1.20.x`, then I am expecting my Addons also gets updated to the supported version of `v1.20.x or the latest one`. This will also hold for patch version updates for example from EKS `v1.19.x to v1.19.y`.
I am expecting some sort of feature flag in the EKS Addons section where users can opt-in for these updates automatically as and when they update their control plane version. This provides control on the user end whether they want to update these components automatically or they prefer the existing wat if doing it which is more manual.

**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?**
Updating the Addons manually after EKS control plane updates becomes very hard and if you have multiple clusters to manage then it becomes impossible to make use of this feature. If I introduce the use of EKS Addons for my clusters then whenever I update my clusters version, I've to manually do the Addons updates which become overhead of multiple clusters.

**Are you currently working around this issue?**
I am not using EKS Addons as managing the manual updates of these components is not possible for multiple clusters.

**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.)

No files, tests, or entry points are named. Start by reviewing the EKS Addons request and how EKS cluster version updates relate to supported addon versions. Done would require an agreed opt-in mechanism and defined behavior for automatic addon updates, including patch and version upgrades.

Written by the indexing model from the issue text.