Initial client side operation timeout (CSOT) work.
The CSOT class is passed to all operations and currently encapsulate the following timeouts:

  - `timeoutMS` the new optional client side operation timeout
  - `maxTimeMS` the legacy maxTimeMS operation value. Ignored if CSOT is set.
  - `maxCommitTimeMS` the legacy commit timeout. Ignored if CSOT is set.
  - `maxAwaitTimeMS` the getMore await timeout.

This initial work allows for the CSOT to be available to all operations and later
work will pass / apply this timeout where required by the Spec.

JAVA-4086

JAVA-4064

# Conflicts:
#	driver-core/src/main/com/mongodb/ConnectionString.java
#	driver-core/src/test/unit/com/mongodb/MongoClientSettingsSpecification.groovy

…terface (#1194)

JAVA-5112

An immutable class that contains all user configured timeouts.
This will eventaually allow access to user configuration down the
stack into Bindings / Cluster.selectServer and Connection.command.

JAVA-5169

JAVA-5175

In preparation for adding all contexts to OperationContext

JAVA-5170

This will allow the timeout settings to be available to the Binding
and this will allow the binding to create the TimeoutContext for the
operation.

JAVA-5170

Now contains RequestContext, SessionContext and TimeoutContext

JAVA-5170

JAVA-5170

Operations now supply TimeoutSettings

JAVA-5170

Pass OperationContext as a whole instead of RequestContext,
SessionContext, TimeoutContext and ServerAPI

JAVA-5170

Adds support for Explainable operations

JAVA-5172

JAVA-5170

# Conflicts:
#	driver-core/src/main/com/mongodb/internal/connection/BaseCluster.java
#	driver-core/src/main/com/mongodb/internal/connection/LoadBalancedCluster.java
#	driver-core/src/test/functional/com/mongodb/ClusterFixture.java
#	driver-core/src/test/unit/com/mongodb/internal/connection/BaseClusterSpecification.groovy
#	driver-reactive-streams/src/main/com/mongodb/reactivestreams/client/internal/ClientSessionBinding.java
#	driver-reactive-streams/src/test/unit/com/mongodb/reactivestreams/client/internal/ClientSessionBindingSpecification.groovy
#	driver-sync/src/test/unit/com/mongodb/client/internal/ClientSessionBindingSpecification.groovy

…#1209)

JAVA-5184

JAVA-5212

JAVA-4065

JAVA-5212

Apply test server selection timeouts to OperationContext
instead of ClusterSettings

The CSOT spec requires the maxTimeMS takes into account
the recent minimum round trip time.

JAVA-5254

Added support for cursor lifetime and cursor iteration
timeout modes.

JAVA-4058

Some tests are racy by nature and this annotation can be used
to retry racy tests a number of times before deciding its a
failure.

JAVA-4058

add and min can be called by different threads
leading to a NPE in the min logic

JAVA-5232

Validates that the timeoutMS is greater than minRoundTrip
Throws a timeout exception if the minRoundTrip is greater
or equal to the remaining timeoutMS

JAVA-5255

JAVA-5262

JAVA-5263

JAVA-5263

Caused by using `doOnError` rather than using `subscribe` and
passing the handler in there.

JAVA-5266

JAVA-5264

…tionNamesPublisher.maxTime

…uce chance of failures

…n for test doc insert

Add client operation timeout to retry functionality.

JAVA-4052

Now returns MongoOperationTimeoutException instances

JAVA-5248

JAVA-5277

JAVA-5258 (#1296)

JAVA-5278

Now the DefaultServerMonitor and the DefaultConntectionPool
have access to their own OperationContext.

Removed additionalTimeout from API. Manipulate the operation context instead.

JAVA-4063

JAVA-5211

This reverts commit 1267f5d.