Fix TestQuit, by only exposing the wrapped exception from pipeline write failures

This is generally yhe behavior we want I think.

StackExchange.Redis/StackExchange/Redis/PhysicalConnection.cs

@@ -270,8 +270,9 @@ public Task FlushAsync()
             return Task.CompletedTask;
         }
 
-        public void RecordConnectionFailed(ConnectionFailureType failureType, Exception innerException = null, [CallerMemberName] string origin = null)
+        public Exception RecordConnectionFailed(ConnectionFailureType failureType, Exception innerException = null, [CallerMemberName] string origin = null)
         {
+            Exception ex = innerException;
             IdentifyFailureType(innerException, ref failureType);
 
             if (failureType == ConnectionFailureType.InternalFailure) OnInternalError(innerException, origin);
@@ -330,7 +331,7 @@ void add(string lk, string sk, string v)
                     add("Last-Global-Heartbeat", "global", ConnectionMultiplexer.LastGlobalHeartbeatSecondsAgo + "s ago");
                 }
 
-                var ex = innerException == null
+                ex = innerException == null
                     ? new RedisConnectionException(failureType, exMessage.ToString())
                     : new RedisConnectionException(failureType, exMessage.ToString(), innerException);
 
@@ -357,6 +358,7 @@ void add(string lk, string sk, string v)
 
             // burn the socket
             Shutdown();
+            return ex;
         }
 
         public override string ToString()
@@ -709,8 +711,7 @@ internal void WakeWriterAndCheckForThrottle()
             }
             catch (ConnectionResetException ex)
             {
-                RecordConnectionFailed(ConnectionFailureType.SocketClosed, ex);
-                throw;
+                throw RecordConnectionFailed(ConnectionFailureType.SocketClosed, ex);
             }
         }