[EKS] [request]: Requesting managed addon for External Secrets Operator

### 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**
What do you want us to build?
EKS Add-on for External Secrets Operator

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
EKS customers would benefit a lot if the [External Secrets Operator](https://external-secrets.io) could be packaged as an Add-on in EKS.
This will benefit customer by making deployment and management of the operator easy.

**Are you currently working around this issue?**
How are you currently solving this problem?
Manually deployment and management of the operator.

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

The issue requests packaging External Secrets Operator as an EKS add-on; no repository files, tests, or implementation entry points are identified. Start by reviewing the EKS add-on requirements and the linked External Secrets Operator project. Done would mean an agreed and implemented managed add-on, but the issue does not define its technical scope or acceptance criteria.

Written by the indexing model from the issue text.