fix(NODE-3197): revert setImmediate in waitQueue (#2802)

A performance regression was identified in switching the connection
pool to using setImmediate instead of process.nextTick for wait
queue processing. This patch reverts that change.

Author: nbbeeken

src/cmap/connection_pool.ts

@@ -245,7 +245,7 @@ export class ConnectionPool extends TypedEventEmitter<ConnectionPoolEvents> {
     }
 
     this[kWaitQueue].push(waitQueueMember);
-    setImmediate(() => processWaitQueue(this));
+    process.nextTick(processWaitQueue, this);
   }
 
   /**
@@ -270,7 +270,7 @@ export class ConnectionPool extends TypedEventEmitter<ConnectionPoolEvents> {
       destroyConnection(this, connection, reason);
     }
 
-    setImmediate(() => processWaitQueue(this));
+    process.nextTick(processWaitQueue, this);
   }
 
   /**
@@ -440,7 +440,7 @@ function createConnection(pool: ConnectionPool, callback?: Callback<Connection>)
 
     // otherwise add it to the pool for later acquisition, and try to process the wait queue
     pool[kConnections].push(connection);
-    setImmediate(() => processWaitQueue(pool));
+    process.nextTick(processWaitQueue, pool);
   });
 }