…e MMAP

…ed suites

This output can be used to run previous schedules when debugging test
failures.

No functional changes, just moving code around.

Currently the write commands explain code calls
ensureShardVersionOKOrThrow, which performs legacy style shard version
checking based on the contents of the connection. This however does not
have any effect, because write commands are not sent over versioned
connections, so effectively write command explain is non-sharding aware
currently.

This change removes this check for the explain commands.

…r in unit tests.

The fetcher test is excluded at present, because it appears to depend on some
implementation behavior of ReplicationExecutor that remains to be diagnosed.

With this change all legacy-style (non-NetworkInterface) communication
from mongos to shard mongod is going through ShardConnection and will
always end the shard initialization data at connection establishment.

…log using Fetcher instead of OplogReader

…command line to resmoke.py

…in sharding code

link the option for callers of ::exec

o run JS_MaybeGC in the interrupt handler
o run manual gc() in DBQuery.itcount()

…ing a collection to force the version to be set

…ssible

Use built-in ES5 function for less error-prone array detection and
limit the number of array elements to 3.