fix(h2): log SET SCHEMA failure instead of swallowing

[Aias00]

Related issue

Closes #2149

Summary

H2DBManager had an empty catch around SET SCHEMA execution, silently swallowing SQLException failures with no log. Added @slf4j and log.error, mirroring sibling DBManagers (OscarDBManager, OracleDBManager, etc.).

Verification

• mvn compile -> BUILD SUCCESS.

Contributor declaration

• I linked the Issue that defines this change.
• I tested the affected behavior and reported the actual results above.
• I did not include credentials, private data, or generated build output.
• I disclosed substantial AI assistance below, or this PR contains no substantial AI-generated code.

AI assistance: The fix, verification, and PR description were produced with Claude Code assistance.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[openai0229]

This is a useful low-risk logging improvement, but the current PR is not ready to merge without validating the exception path it changes.

Please add a focused H2DBManager test where Connection.setSchema throws SQLException and verify that connectDatabase contains the failure without propagating it. If the project test setup supports log capture, assert the schema name and exception are logged; otherwise document why the log itself is not asserted. Please rebase onto the latest main; #2177 also modifies H2DBManager, so whichever PR lands second must resolve that overlap.

[openai0229]

The changed SQLException path still lacks a focused H2DBManager regression test, and this branch overlaps open PR 2177. The current head does not address the detailed review comment already posted, so this remains blocked pending an updated commit and re-review.

[Aias00]

Rebased onto latest main. Added 2 regression tests in H2DBManagerTest:

1. connectDatabaseCatchesSQLExceptionForBadSchema — sets a non-existent schema name, verifies connectDatabase catches the SQLException (log shows: 'Failed to set schema: NONEXISTENT_SCHEMA_12345') and does not propagate it.
2. connectDatabaseReturnsEarlyWhenSchemaNameIsBlank — verifies the early-return path when schemaName is blank.

Tests run: 2, Failures: 0. The log output confirms the schema name and exception are logged via log.error.