fix(jdbi): publish jdbi bom to consumers

[graemerocher]

Summary

• publish the Jdbi BOM from micronaut-jdbi so downstream Jdbi modules resolve against the same managed version
• keep jdbi3-core on the managed version while exporting the BOM transitively for consumers
• verify the module tests and a scratch downstream consumer resolve jdbi3-sqlobject through the transitive BOM

Verification

• ./gradlew :micronaut-jdbi:test
• ./gradlew -p /tmp/mn-jdbi-repro-avVwx2 --refresh-dependencies resolveRuntime
• ./gradlew -p /tmp/mn-jdbi-repro-avVwx2 --refresh-dependencies dependencyInsight --dependency org.jdbi:jdbi3-sqlobject --configuration runtimeClasspath

Resolves #839

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Publishes the Jdbi BOM from micronaut-jdbi so downstream consumers can resolve Jdbi artifacts against a consistent, managed version set.

Changes:

• Add the Jdbi3 BOM as an api(platform(...)) dependency in micronaut-jdbi.
• Keep jdbi3-core as an api dependency while relying on the BOM for version alignment.

[radovanradic]

verify the module tests and a scratch downstream consumer resolve jdbi3-sqlobject through the transitive BOM

Like Copilot comment suggests, it does not bring jdbi3-sqlobject dependency with version from BOM unless explicitly added