Play Framework

fix(db): case-insensitive module_key column check in Evolutions (PF-143)

checkAndUpdateEvolutionsForMultiModuleSupport probed for the module_key
column with a lowercase getColumns() pattern, which finds nothing under
H2's default UPPERCASE metadata (the framework's own default DB) and
wrongly re-runs the ALTER, throwing a swallowed duplicate-column error
that hides applied revisions. Replaced with a case-insensitive
hasModuleKeyColumn() that enumerates columns under both name casings
(mirrors the uppercase fallback in isEvolutionsTableExist). Also closes
a pre-existing unclosed-ResultSet leak.

Tests: dropped the DATABASE_TO_LOWER=TRUE crutch from EvolutionsTest so
the 4 cases run under default H2 casing (which is what proves the fix),
and made tableExists() case-insensitive. The legacy single->multi-module
upgrade test is deferred to PF-144: alterForModuleSupport has a separate
dialect bug (nullable column added to the PK) that silently half-fails
under H2; a clean upgrade test lands with that fix.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>