[Subtask] Complete V3 type compatibility for the Trino connector

### Describe the subtask

Complete and document the five-family compatibility contract for Trino 435 through 478.

**Compatibility outcomes**

- **Nanosecond timestamps:** Reject before Iceberg delegation.
- **Variant:** Reject because supported Trino versions have no faithful equivalent.
- **Unknown/Null:** Reject as an invalid persisted column type.
- **Geometry:** Reject rather than lose spatial semantics.
- **Geography:** Reject rather than lose CRS or edge-algorithm semantics.

**Acceptance**

- Reproduce all five families through the connector's public create/conversion path and its alter/load paths where supported.
- A supported mapping must round-trip without losing type identity or parameters.
- An unsupported mapping must return `IllegalArgumentException` before external metadata mutation; no fallback to a narrower or opaque type is allowed.
- Cover nested types where the connector supports complex columns.
- Add focused converter/operation tests and an integration or no-side-effect test appropriate to the connector.
- Update the connector documentation with a five-family compatibility matrix and rejection rationale.
- Keep implementation commits atomic by connector and type family.

**Connector-specific verification**

Pass each type through `IcebergDataTypeTransformer`, verify `GRAVITINO_ILLEGAL_ARGUMENT`, and prove the delegated connector is never invoked. Cover bidirectional adapters, the default suite, and Trino 478.

**Documentation**

`docs/trino-connector/catalog-iceberg.md`

### Parent issue

#12056