avoid sqlite3 time quoting failures (due nil zone) while testing with AR 2.3
allow test_jdbc to fail on travis - not sure why we can't connect to MySQL
localhost using the plain JDBC method while using mysql_connection works
although they seem just the same (and connections works locally)
retry makes no sense during rollback (should use the very same connection)
update appraised dependencies (mainly 4.0 beyond beta1) and mocha
4.0 has issues with doing a `DbType.create` fails to generate correct SQL
[sqlite3] update (missing functionality helper) rename table from AR-4.0
otherwise it was failing with 4.0 - mostly due missing id: false option ...
deprecate SQLBlock class in favor of a parameterized Callable interface
AR-4.0 transaction isolation support (Java API) + some related refactoring :
- we allow #supports_transaction_isolation? with the isolation level param
- updated #begin to accept an optional isolation level argument
- correct SQL exception handling for #begin #commit and #rollback
- new #withConnection (as a replacement for #withConnectionAndRetry)
  * now retries even if getAutoCommit fails with an error
  * allow for (automatic) exception handling to be turned off
- #wrapException (a rename of #wrap) and #handleException helpers
a long needed (Java) code cleanup
4.0 transaction isolation support (Ruby part) with tests the holy 3 adapters
tests fail for now due count expecting AR::Result on 4.0 (not implemented)
a few sqlite3 adapter supports_"features" copied from master