[Feature] Trino Connector

### Willingness to contribute

{"label"=>"No. I cannot contribute a bug fix at this time.", "value"=>"cannot_contribute"}

### Feature Request Proposal

Are you planning to add trino connector

### Motivation

Similar use case as using Spark that you currently support

### What component(s) does this feature affect?

- [X] `Table Service`: This is the RESTful catalog service that stores table metadata. `:services:tables`
- [X] `Jobs Service`: This is the job orchestrator that submits data services for table maintenance. `:services:jobs`
- [X] `Data Services`: This is the jobs that performs table maintenance. `apps:spark`
- [X] `Iceberg internal catalog`: This is the internal Iceberg catalog for OpenHouse Catalog Service. `:iceberg:openhouse`
- [ ] `Spark Client Integration`: This is the Apache Spark integration for OpenHouse catalog. `:integration:spark`
- [ ] `Documentation`: This is the documentation for OpenHouse. `docs`
- [ ] `Local Docker`: This is the local Docker environment for OpenHouse. `infra/recipes/docker-compose`
- [ ] `Other`: Please specify the component.

### Details

_No response_

Start by reviewing the existing Spark support in :services:tables, :services:jobs, apps:spark, and the Iceberg internal catalog. The issue names no files or tests, so first map how those components integrate and identify the relevant entry points. Done would require an agreed Trino connector design spanning the affected components.

Written by the indexing model from the issue text.