Move the old test suite away
Revise db/collection access PHP-667 test
Fixed PHP-355: Driver does not honour connection 'timeout'

Previous fix to PHP-356 fixed the timeout for creating the actual
connection, while this fix deals with timeout for the ping/pong game we
need to play with mongod when bootstrapping the connection.

Note: These are two (three) different options!
connectTimeoutMS is exclusively used for connecting to the server
socketTimeoutMS  is used for data transmissions
and the 3rd one
wTimeoutMS       is _server side_ replication timeout

The socketTimeoutMS can be adjusted per-query, while connectTimeoutMS
can only be set in the ctor.
The connectTimeoutMS is is also used when attempting to reestablish
connection to the server after f.e. query timeout (socketTimeoutMS).

To make things consistent we should probably consider allowing
"socketTimeoutMS" as a query options, today it is simply called
"timeout" which is a littlebit ambiguous
Changed signature of mongo_io_recv_data() to be the same as mongo_io_recv_header().

Keeping our APIs consistent since 2012 :-)
Fixed PHP-688: Default connect() timeout is 1000 _seconds_, not
milliseconds

uhh, no. The default was never 1000 seconds

The caller used to send 1000 *ms* as the default, not seconds.
Since the caller was hardcoded this check never kicked in until now
We support timeouts now, use it
Make sure we print something out when this test fails

Also update the errormessage which seems to be have improved in certain
cenarios in 2.3.x

The first and the last connection hashes were actually identical and
therefore pretty meaningless, so made sure all 3 are unique
Fixed PHP-691: Memory leak during master failover

MongoCollection->update() & remove() do not have this problem
Initial utility files for a new test infrastructure

This new structure only requires one config option,
/path/to/mongo/shell.
ReplicaSets, Shards & standalone servers can be spun up ondemand and
torn down when needed.
Failover testing is also possible, network partitioning and whatever
else the shell testing framework is capable of
Initial tests, demonstrating ReplicaSet testing & ReplicaSet failover
Move one of the original tests back to see what sort of BC layer needs
to be created
Update test to work with the new test suite, and add some BC functions
Rename into a legacy folder
Rename back into the test folder
Update to support the new test suite
More BC stuff to support the old tests
This is an annoyingly slow test
Improve the test failure ignores
Rename test back into its place
Update to support legacy tests in the new test suite