Adding new JDBC - Other driver does not guard against invalid jdbc connection string

Adding a new JDBC - Other datasource with an invalid JDBC Connection string successfully adds the datasource but any attempt to use that datasource results in an internal Lucee NPE.

This is due to an invalid connection string being passed to the JDBC driver that can result in null being returned by DataSourceSupport._getConnection(). This is turn in is not checked by DataSourceSupport.getConnection() which results in Lucee ending up with a DataSource with a null connection.

This then falls over when the Connection is attempted to be retrieved in DCStack.openConnectionsIn()

Suggest that DataSourceSupport.getConnection() add a null check and throw a RuntimeException to prevent an invalid DataSource from being created.

Found as a result of investigation in https://dev.lucee.org/t/using-ucanaccess-with-lucee-5/2594