Remediate dependency vulnerabilities via Moderne recipes and align project dependency baselines

[Copilot]

This PR addresses the security-remediation issue by reducing known vulnerable dependency exposure using automated Moderne migrations, focusing on vulnerable/outdated components in the Maven dependency graph.

• Dependency security remediation (Maven properties)

  • Upgraded core dependency version properties in pom.xml to pull in newer, safer transitive sets:
    • dropwizard.version: 4.0.2 → 5.0.2
    • h2.version: 2.2.224 → 2.4.240
  • This targets vulnerable component remediation through BOM/property-driven dependency convergence rather than ad hoc direct overrides.

• Moderne migration/context updates

  • Applied migrations using Moderne recipe execution (MCP/CLI path).
  • Refreshed .moderne/context/* outputs after migration so repository context reflects the updated dependency/security posture.
  • Included generated context updates (including new dependency usage/library usage artifacts) from the Prethink refresh run.

• Representative change

  <properties>
      <dropwizard.version>5.0.2</dropwizard.version>
      <h2.version>2.4.240</h2.version>
  </properties>

This change was produced with Moderne CLI and Moderne Agent Tools (MCP), informed by Moderne Prethink context (dependencies, test gaps, project identity).