ConnectionPool::getConnection accepts one parameter to set how many milliseconds a connection can take, however the logic within may shorten the timeout to the controller's pending timeout.

During multiple discussion it isn't clear if this is still needed and why, removing it causes few ConnectionPool executor_tests fail.

amirsaman.memaripour@mongodb.com also brought up the point that it doesn't make much of a difference when this method, which is purely responsible for acquiring a connection to its peer, take longer than 20 seconds.

The acceptance criteria for this ticket is to define if ConnectionPool should interfere with its given timeout, and if not, remove it.