Allow Data JDBC Dialect resolution without requiring DataSource initialization

When obtaining a Dialect bean using Spring Data JDBC, the @Bean method depends on NamedParameterJdbcOperations leading to initialization of the entire bean graph including DataSource initialization even if the dialect is provided through properties (spring.data.jdbc.dialect=…). It would be good if access to NamedParameterJdbcOperations could be lazy.

The JDBC config itself isn't helpful in that regard as it declares NamedParameterJdbcOperations in its signature. Maybe an opportunity for improvement as well.

Start by tracing the JDBC configuration and the @Bean method that resolves the Dialect, then inspect how its NamedParameterJdbcOperations parameter triggers DataSource initialization. Done means a dialect supplied by spring.data.jdbc.dialect can be obtained without initializing DataSource while the configuration remains functional; check or add focused tests around that startup path.