Add local Trino DuckLake smoke benchmark

[bill-ph]

Summary

• add a pinned, single-node Trino + Brikk DuckLake service to the local integration Compose stack
• give local Trino dedicated PostgreSQL metadata and MinIO reader identities with no write permissions
• add a hermetic smoke test plus opt-in narrow and production-shaped local Duckgres-versus-Trino performance runs
• configure DuckDB and Trino tests for UTC timestamp partition semantics and record version/performance artifacts under artifacts/

Why

This establishes a checksum-validated local compatibility and performance baseline for Trino reading the same DuckLake catalog and data created by Duckgres. It keeps the test fully local and isolated from managed-warehouse infrastructure.

Validation

• just lint
• just trino-ducklake-smoke
• just perf-trino-ducklake-realistic
• docker compose -f tests/integration/docker-compose.yml config --quiet
• git diff --check

[github-actions]

Test Impact Plan

Deterministic summary of how this PR changes tests, CI runners, and coverage-risk signals.

Summary

Area	Added	Changed	Deleted
Test files	7	1	0
E2E/journey files	0	0	0
Workflow files	0	0	0

Signals

• Test cases: +8 / -0
• Assertions: +54 / -0
• Skips or known failures added: 2
• Workflow continue-on-error added: 0
• Workflow path filters added: 0
• Test commands removed from justfile: 0
• E2E/journey retry lines added: 0

Coverage risk: likely reduced

Warnings

• New skips or known failures (likely reduced)
  • 2 skip/allowlist line(s) added