feat(connection-spy): add class for monitoring active connections

This gives us more control over the process of monitoring active
and removed connections in a given topology. This also allows for
an event-driven approach to cleanup, whereas in the past we have
depended upon timeouts.

NODE-1132

Author: mbroadst

test/tests/functional/shared.js

@@ -1,4 +1,5 @@
 'use strict';
+const EventEmitter = require('events');
 
 function executeCommand(configuration, db, cmd, options, cb) {
   var Pool = require('../../../lib/connection/pool'),
@@ -104,6 +105,38 @@ const delay = function(timeout) {
   });
 };
 
+class ConnectionSpy extends EventEmitter {
+  constructor() {
+    super();
+    this.connections = {};
+  }
+
+  addConnection(id, connection) {
+    // console.log(`=== added connection ${id} :: ${connection.port}`);
+
+    this.connections[id] = connection;
+    this.emit('connectionAdded');
+  }
+
+  deleteConnection(id) {
+    // console.log(
+    //   `=== deleted connection ${id} :: ${this.connections[id] ? this.connections[id].port : ''}`
+    // );
+
+    delete this.connections[id];
+    this.emit('connectionRemoved');
+
+    if (this.connectionCount() === 0) {
+      this.emit('drained');
+    }
+  }
+
+  connectionCount() {
+    return Object.keys(this.connections).length;
+  }
+}
+
 module.exports.executeCommand = executeCommand;
 module.exports.locateAuthMethod = locateAuthMethod;
 module.exports.delay = delay;
+module.exports.ConnectionSpy = ConnectionSpy;