Support existing bootstrap experience with new JDBC module

### Describe the bug

please ref : https://github.com/apache/polaris/pull/1371#discussion_r2059531495

Essentially for multiple realms with 1 Datasource per realm we need to pre-configure quarkus before running the bootstrap tool, we should restore the prev experience where eclipselink didn't required it.

### To Reproduce

_No response_

### Actual Behavior

_No response_

### Expected Behavior

_No response_

### Additional context

_No response_

### System information

_No response_

Start by reading the referenced discussion in PR #1371 and the new JDBC module's bootstrap path. Trace how Quarkus is configured for multiple realms with one datasource per realm, and compare this with the previous EclipseLink experience. Done means the bootstrap tool supports that existing experience without requiring manual pre-configuration.

Written by the indexing model from the issue text.