Use JdbcConnectionDetails to detect Dialect instead of Environment

[making]

closes gh-286

[making]

@backpaper0
I support obtaining the URL from JdbcConnectionDetails because I want to automatically detect it from TestContainers and Docker Compose as well.
If JdbcConnectionDetails cannot be obtained, what behavior do you think would be appropriate?
For example, if DataSource is explicitly defined, JdbcConnectionDetails is not generated by AutoConfiguration.
The following options can be considered:

• Inject DataSourceProperties as an alternative. This prevents errors from occurring, but DataSourceProperties may not hold accurate values in this use case, so an incorrect dialect might be detected.
• Generate an error and encourage users to explicitly specify doma.dialect. This would be a breaking change, but it might be safer.

[backpaper0]

@making
Thank you.
I’d prefer the latter option.
As long as we clearly explain a breaking changes in the release notes, it shouldn’t be a problem.