[trino] Add native read-only Trino connector

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.

### Description

## Motivation

Apache Fluss currently has no native Trino connector for querying Fluss-managed data directly.

Previous work in #1810 and FIP-18 explored a broader Trino integration, including Lakehouse Union Read and multi-version support.

This issue tracks a narrower first step: a native, read-only Trino connector for Fluss.

## Scope

The initial connector focuses on:

- metadata discovery and type mapping;
- bounded reads of non-Lakehouse Log Tables;
- current-state reads of non-Lakehouse Primary Key Tables;
- projection and predicate-based scan optimizations;
- partition/bucket pruning and primary-key lookup where applicable.

Lakehouse Union Read, Lakehouse format readers, writes/DDL, and Trino core changes are intentionally out of scope.

## Design

Detailed design and discussion:

- FIP-XXX: Native Read-Only Trino Connector for Apache Fluss
- Design doc: https://docs.google.com/document/d/1mY-PN8KY1cJSD9YzISuL14A6rEIH1Htj9l99XrLmPk0
- Discussion thread: https://lists.apache.org/thread/275nbvz6w2288ky9mq70962nscvxm54o

## Prior Work

- #1810
- FIP-18
- PR #1923

### Willingness to contribute

- [x] I'm willing to submit a PR!

Start with the FIP-XXX design, linked design document, discussion thread, and prior work in #1810, FIP-18, and PR #1923. Done means a read-only connector covering metadata and type mapping, bounded non-Lakehouse reads, current-state Primary Key reads, and the listed scan and pruning optimizations while leaving writes, DDL, Lakehouse reads, and Trino core changes out of scope.

Written by the indexing model from the issue text.