feat: Remove the need to specify dbDriver for external databases using JDBCv4 ServiceLoader supporting JDBC drivers

[aikebah]

Fixes Issue #6937

Description of Change

• Remove the pre-configured dbDriver so that no dbDriver override is required
• Update documentation to more clearly specify that dbDriver specification is only required in specific scenarios
• Issue a warning message when detecting explicit dbDriver configuration for a JDBC driver that is on the classpath

Have test cases been added to cover the new functionality?

no, a sensible test would require an external database server. Used the local test-project that surfaced the issue for validating the solution working with an external database. Existing test-cases proof that the removal of the dbDriver configuration is not affecting the use of the embedded h2 database (as the H2 driver is also fully supporting the JDBCv4 ServiceLoader mechanism).

[jeremylong]

ack - merge conflicts that will likely take using beyond compare to figure out ;)

[aikebah]

@jeremylong I'll work on rebasing it to get rid of them... most likely effect of my editor autoformatting the file on edit

[aikebah]

IntelliJ IDEA with ignoring whitespace made the merge-conflict resolution easily.... a typo fix and addition of a missing path were the conflicting changes

[jeremylong]

Beyond Compare's diff would have been similar - if you ever have to diff a lot of code I always prefer using BC4. It is hands down the best diff tool available.

[aikebah]

Up to now I've been quite satisfied with the 3-way merge of IntelliJ IDEA for resolving merge conflicts, but I do know that BeyondCompare is also a strong tool though I've never used it.