Database migration uses the "deprecated" o.j.d.OracleDriver

Problem Definition

Bitbucket Server config properties documents using oracle.jdbc.driver.OracleDriver, which has been deprecated by Oracle. The system, and the documentation, should be updated to reference oracle.jdbc.OracleDriver, the documented replacement:

Desupport of oracle.jdbc.driver
In the initial release of the Oracle JDBC drivers customers were
advised to use the classes defined in the package
oracle.jdbc.driver. This has caused problems for customers and for
Oracle. In Oracle JDBC release 9.0.1 customer use of the classes
in that package was deprecated. A new package, oracle.jdbc, was
introduced and customers were advised to begin using the
interfaces and classes defined in oracle.jdbc. In every release
since 9.0.1 we have encouraged customers to switch to oracle.jdbc
and stated that oracle.jdbc.driver would be desupported. The time
has come. Customer code that references oracle.jdbc.driver will
not compile and will not execute in this and future releases of
the Oracle JDBC drivers. Please use oracle.jdbc instead.

(Quote is from here.)

Suggested Solution

• Update the driver Class to oracle.jdbc.OracleDriver in the Database/jdbc.driver section.
• Update the system to use oracle.jdbc.OracleDriver during migration
• Update the system to detect the legacy o.j.d.OracleDriver class and automatically switch to o.j.OracleDriver at runtime