net: fix autoSelectFamily close behavior

If the first connection is successful, but only after the connect
timeout, and all subsequent connections result in an error, the socket
will not emit the 'close' event, causing issues in places like 'http's
'Agent' which rely on the 'close' event to free up sockets.

This commit moves the reassignment of '_handle' to happen as soon as a
new connection is attempted, so that if the socket is destroyed, the
'_handle' will represent the last connection attempt (even if it
resulted in an error) and closing the handle will then cause the 'close'
event to be emitted.

See npm/cli#6409 for more background.

Author: dharesign

lib/net.js

@@ -1112,6 +1112,11 @@ function internalConnectMultiple(context, canceled) {
   let localAddress;
   let err;
 
+  if (context.current > 1 && self[kReinitializeHandle]) {
+    self[kReinitializeHandle](handle);
+    handle = self._handle;
+  }
+
   if (localPort) {
     if (addressType === 4) {
       localAddress = DEFAULT_IPV4_ADDR;
@@ -1621,11 +1626,6 @@ function afterConnectMultiple(context, current, status, handle, req, readable, w
     return;
   }
 
-  if (context.current > 1 && self[kReinitializeHandle]) {
-    self[kReinitializeHandle](handle);
-    handle = self._handle;
-  }
-
   if (hasObserver('net')) {
     startPerf(
       self,