Add Turso (SQLite-compatible) database support

[velo]

Summary

Adds Turso (an in-process, SQLite-compatible database) as a Querydsl SQL backend, mirroring the existing SQLite support.

Main source (querydsl-sql)

• TursoTemplates — SQL dialect (clone of SQLiteTemplates, uses Keywords.TURSO)
• keywords/turso resource + Keywords.TURSO
• SQLTemplatesRegistry maps the turso JDBC product name to TursoTemplates.builder()
• tech.turso:turso:0.6.0 JDBC driver wired as a test dependency (jdbc:turso: URL, driver tech.turso.JDBC)

Test infrastructure

• Target.TURSO, testutil.Turso marker (embedded-DB category, runs under -Pdev/CI like SQLite)
• Connections.getTurso() / initTurso()
• TursoTemplatesTest, TursoSuiteTest, TursoLiteralsSuiteTest, ExportTursoTest
• JPA Mode, DateArithmeticTest, KeywordQuotingBase, FilterFactory, MatchingFiltersFactory updated for the new target

Test results

Full SQL integration suite against Turso 0.6.0: 194 pass / 78 fail / 33 skip.

The 78 failing tests are excluded for TURSO via @ExcludeIn(TURSO) (ExportTursoTest is @Disabled) and tracked in #1812, grouped by gap (missing functions, Long/Double DECIMAL conversion, qualified columns in DML, FOR UPDATE, FULL OUTER JOIN, java.time setObject, incomplete JDBC metadata, …) with links to existing upstream Turso issues where they exist. No new issues were opened on the Turso repo.

Turso closes the shared JDBC connection when a statement errors, so AbstractBaseTest reconnects per-test for TURSO to prevent a single failure cascading across the suite.

Regression run of the embedded suites (H2, HSQLDB, Derby, SQLite, Turso): 3513 tests, 0 failures (only the pre-existing unrelated QueryPerformanceTest JMH-harness error).

Closes nothing; tracked by #1812.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPLya3e3DqdYmfdaoH3L6o