Add Java and driver versions to SQL error report

[DG47]

Fixes #267

The SQL error report (errorReportSql.txt) now includes the Java version and, as suggested in the issue comments, the driver version:

• Java version, from java.lang.System.getProperty("java.version").
• For JDBC connections: the JDBC driver name and version from DatabaseMetaData (for example PostgreSQL JDBC Driver (42.7.3)).
• For DBI connections (DuckDB, SQLite, or a plain DBI connection passed to querySql() / executeSql()): the DBI driver package and its version (for example duckdb (1.5.6)).

These lines appear after Platform: in the system info section. Each lookup is wrapped in tryCatch() and falls back to Unknown, so the report is still written when the connection is broken.

.createErrorReport() has a new optional connection argument, and all five call sites (executeSql() twice, querySql(), renderTranslateQueryApplyBatched(), and querySqlToAndromeda()) pass the connection. Nothing else changes, and NEWS.md is not touched.

Example report section (Postgres):

Platform:
aarch64-apple-darwin27.0.0

Java version:
17.0.20.1

JDBC driver:
PostgreSQL JDBC Driver (42.7.3)

Attached base packages:
...

Tests: the new tests/testthat/test-errorReport.R loops over the test servers and checks the report for both JDBC connections (Postgres) and DBI connections (SQLite, DuckDB). It also has one test with a plain duckdb DBI connection. I ran it against PostgreSQL 16 in Docker plus the local SQLite and DuckDB servers. It fails on develop and passes with this change. R CMD check --no-manual --ignore-vignettes gives Status: OK.