[Bug report] Trino connector JUnit integration tests never run in CI

### Version

main branch

### Describe what's wrong

The Trino integration workflow only runs the SQL-file harness (`trino_integration_test.sh` -> `:trino-connector:integration-test:TrinoTest`). No step runs `:trino-connector:integration-test:test`, so the JUnit ITs in that source set, including `TrinoUDFIT`, have never executed.

`TrinoUDFIT` asserts exactly the behaviour that is broken (SHOW FUNCTIONS and invocation of a registered SQL function) and would have failed on its first run. It also waits for `show catalogs` to contain `.`, which never appears because the IT environment runs the connector in single-metalake mode.

The unit tests in `TestGravitinoMetadataFunction` pass only because they assert that `LanguageFunction::sql` comes back byte-for-byte as stored, i.e. they assert the pass-through that is the defect.

### Error message and/or stacktrace

N/A

### How to reproduce

Run `./gradlew :trino-connector:integration-test:test -PskipDockerTests=false` locally: `TrinoUDFIT` fails with `Catalog gt_hive_udf sync timeout`.

### Additional context

The JUnit ITs should run in the Trino integration workflow alongside the existing harness.

Start by running ./gradlew :trino-connector:integration-test:test -PskipDockerTests=false and read TrinoUDFIT alongside trino_integration_test.sh. Trace the Trino integration workflow and its single-metalake setup, then ensure the JUnit integration tests run with the existing harness and no longer fail on the catalog sync timeout.

Written by the indexing model from the issue text.