[EKS] [request]: Trino as a native add-on for EKS clusters

### 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 would like to request Trino as a native add-on for EKS clusters.

The goal is to run distributed SQL query workloads directly on EKS while keeping cluster management centralized and aligned with our Kubernetes-first and GitOps operating model.

As AWS continues moving toward an application-first cluster experience, having Trino delivered as a managed EKS add-on would significantly simplify deployment, scaling, and lifecycle management.

**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?**
Today, deploying Trino on EKS requires custom Helm deployments, manual configuration, and ongoing version management outside the standard EKS lifecycle.

This introduces operational overhead and inconsistency across environments.

If Trino were available as an EKS add-on, it could be enabled directly during cluster creation (via Terraform, eksctl, or the AWS Console), simplifying provisioning and long-term management.

An add-on model would help us:

1. Align fully with our Kubernetes-first architecture
2. Reduce operational complexity compared to managing custom Helm deployments
3. Simplify version upgrades and configuration management
4. Standardize environment setup across dev, staging, and pro
5. Enable centralized logging and metrics integration with CloudWatch by default

**Are you currently working around this issue?**
We are currently deploying Trino using Helm charts and managing configuration, scaling, IAM, and upgrades manually.

While functional, this introduces additional operational steps and requires ongoing maintenance across environments.

A managed EKS add-on would streamline deployment, reduce setup time, and make Trino feel like a native component of the cluster lifecycle rather than an externally managed application.

The request names EKS, Helm, Terraform, eksctl, and the AWS Console but no repository files or tests. Start by examining how existing EKS add-ons are represented and how Trino is currently deployed with Helm. Done would require a defined native add-on proposal covering provisioning, scaling, IAM, upgrades, and CloudWatch logging and metrics.

Written by the indexing model from the issue text.