[EPIC] Support Trino 479–483 in the Trino connector

### Describe the proposal

Extend the Trino connector to support Trino 479 through 483.

Compiling the shared connector source against each SPI release shows the
wrapped SPI surface changes across the range. Because each version-segment
module ships one jar built against one SPI version, a single jar cannot
span these changes — so the range needs FOUR modules:

| Module | Distinct wrapped surface vs 478 |
|----------|----------------------------------------------------------------------|
| 479 | none (identical to 478) |
| 480 | getComment() -> Optional; SchemaFunctionName accessors renamed |
| 481 | + finishTableExecute void -> Map |
| 482-483 | + getSplits/getNextBatch, page source/sink, Constraint, JSON serde |

The 480+ breaks land in shared code, so a shared version seam is built
first and the 480/481/482-483 modules build on it.

### Task list

- [x] #12630
- [x] #12633
- [x] #12636
- [x] #12637
- [x] #12638

Start with the shared connector source and the version-segment modules, then compare their wrapped SPI surfaces for Trino 479 through 483. Review the completed task items for existing seams and module boundaries. Done means four modules compile against the required SPI releases and support the listed 480, 481, and 482–483 changes.

Written by the indexing model from the issue text.