Add logic to Derby.getDefaultDriver() to check for availability of different driver classes

[AlexanderSashchenko]

Description

Newer versions of derby use a new driver name, and the old driver is no longer available.

Fix for Derby getDefaultDriver() method to load appropriate driver classes based on db version.

Fixes #1835

[nvoxland]

The change looks good. I did an auto-reformat and added in a comment that got lost.

[nvoxland]

Code review and test results:

Things to be aware of

• Behavior difference is derby 10.15 vs. earlier
• Uses the same "look for the different possible classes in the classloader" trick that we do in MysqlDatabase for a similar problem
• Only impacts derby

Things to worry about

• Nothing

[AlexanderSashchenko]

Tested manually these changes against Apache Derby remote (server-based) database using 10.14 and 10.15 versions. Everything works fine.

[FBurguer]

For this PR, i tested running liquibase with Derby 10.14 vs Derby 10.15 drivers, first in a "in memory" DB and after that with a Docker container. In both environments, liquibase has the same behavior with Derby 10.14 and Derby 10.15.
Test Environment:
Windows 10
Java 11
Docker image: az82/docker-derby