so we don't use up too much in the way of Travis/CI resources

Also don't bother testing MVCC mode, since that's going to go away at
some point, and it's certainly not a default setting for us

turn off partial writes in TestReorderWrites for now, there is a bug
causing massive memory usage increases (for some reason, only when the
test is run in the context of TestAll)

found by running TestRandomSQL for long periods of time

Added BITGET function

Migrate to Travis container-based infrastructure

Sine we're not using sudo we can migrate to the container-based Travis
build infrastructure [1]. This has the following advantages:

 - Builds start in seconds
 - More available resources
 - Better network capacity, availability and throughput
 - Caching available for open source projects

The builds will still fail due to an `OutOfMemoryError` but that's a
different issue.

 [1] https://docs.travis-ci.com/user/migrating-from-legacy/

Added new BITGET function, that returns true if and only if a specified bit in a long is set. This helps simulate bit fields in H2, which is an approach I'm using to significantly shrink database size.

reported by Alexander (vraimax2016)

spatial key fix for null geometries

since it breaks all the tests.

this reverts commit 37641c9a

Table alias get lost on joins

Handle LocalTime with nanosecond resolution

TestMemoryUsage would sometimes manage to overrun it's loop bounds and
enter an infinite loop.

TestMultiThread would sometimes timeout if the machine was busy.

TestOutOfMemory could sometimes fail, and would then cause future tests
to fail because it held onto the memory.

FilePathReorderWrites was not deleting it's subsidiary memFS: data.

TestPreparedStatement::testDateTime8 had a typo.

The change to TestMVStore::testCacheSize I'm not sure about.

Recover for "page store" H2   breaks LOBs consistency

Run tests on Travis

Run the tests on Travis so that when a pull request breaks some tests
we notice it immediately.