Make testSSLHandshakeErrorPropagation less flaky

### Motivation

- The `testSSLHandshakeErrorPropagation` has a very short connect timeout (100ms). The reason for this is, that a failing TLS handshake manifest in NIOTS as a connect timeout and we don’t want to wait for the timeout for to long in our tests.
- Using a the NIOSSL however we expect a proper NIOSSLError. Sometimes though the connection is not setup fast enough (because of the very short 100ms connect timeout), that we get a connectionTimeout error instead.

### Modifications

- Setting the short connect timeout to 100ms when using NIOTS only. This will make sure we get the proper NIOSSLError when using NIOSSL

Author: fabianfett

Diff for: Tests/AsyncHTTPClientTests/HTTPClientTests.swift

@@ -2715,9 +2715,14 @@ class HTTPClientTests: XCTestCase {
             XCTAssertNoThrow(try server.close().wait())
         }
 
-        // We set the connect timeout down very low here because on NIOTS this manifests as a connect
-        // timeout.
-        let config = HTTPClient.Configuration(timeout: HTTPClient.Configuration.Timeout(connect: .milliseconds(100), read: nil))
+        var timeout = HTTPClient.Configuration.Timeout(connect: .seconds(10))
+        if isTestingNIOTS() {
+            // If we are using Network.framework, we set the connect timeout down very low here
+            // because on NIOTS a failing TLS handshake manifests as a connect timeout.
+            timeout.connect = .milliseconds(100)
+        }
+        
+        let config = HTTPClient.Configuration(timeout: timeout)
         let client = HTTPClient(eventLoopGroupProvider: .shared(self.clientGroup), configuration: config)
         defer {
             XCTAssertNoThrow(try client.syncShutdown())