DRIVERS-3181 fix timeouts in CSE custom endpoint test (#1791)

Author: kevinAlbs

source/client-side-encryption/tests/README.md

@@ -811,7 +811,7 @@ Configure with KMS providers as follows:
          "endpoint": "doesnotexist.invalid:443"
       },
       "kmip": {
-         "endpoint": "doesnotexist.local:5698"
+         "endpoint": "doesnotexist.invalid:5698"
       }
 }
 ```
@@ -866,13 +866,12 @@ The method of passing TLS options for KMIP TLS connections is driver dependent.
     Expect this to succeed. Use the returned UUID of the key to explicitly encrypt and decrypt the string "test" to
     validate it works.
 
-4. Call `client_encryption.createDataKey()` with "aws" as the provider and the following masterKey:
+4. Call `client_encryption.createDataKey()` with "kmip" as the provider and the following masterKey:
 
     ```javascript
     {
-      region: "us-east-1",
-      key: "arn:aws:kms:us-east-1:579766882180:key/89fcc2c4-08b0-4bd9-9f25-e30687b580d0",
-      endpoint: "kms.us-east-1.amazonaws.com:12345"
+      "keyId": "1",
+      "endpoint": "localhost:12345"
     }
     ```
 
@@ -961,7 +960,7 @@ The method of passing TLS options for KMIP TLS connections is driver dependent.
     validate it works.
 
     Call `client_encryption_invalid.createDataKey()` with the same masterKey. Expect this to fail with a network
-    exception indicating failure to resolve "doesnotexist.local".
+    exception indicating failure to resolve "doesnotexist.invalid".
 
 11. Call `client_encryption.createDataKey()` with "kmip" as the provider and the following masterKey:
 
@@ -980,11 +979,11 @@ The method of passing TLS options for KMIP TLS connections is driver dependent.
     ```javascript
     {
       "keyId": "1",
-      "endpoint": "doesnotexist.local:5698"
+      "endpoint": "doesnotexist.invalid:5698"
     }
     ```
 
-    Expect this to fail with a network exception indicating failure to resolve "doesnotexist.local".
+    Expect this to fail with a network exception indicating failure to resolve "doesnotexist.invalid".
 
 ### 8. Bypass Spawning mongocryptd
 
@@ -1746,7 +1745,7 @@ Expect an error indicating TLS handshake failed due to an invalid hostname.
 Call `client_encryption_no_client_cert.createDataKey()` with "azure" as the provider and the following masterKey:
 
 ```javascript
-{ 'keyVaultEndpoint': 'doesnotexist.local', 'keyName': 'foo' }
+{ 'keyVaultEndpoint': 'doesnotexist.invalid', 'keyName': 'foo' }
 ```
 
 Expect an error indicating TLS handshake failed.
@@ -1858,7 +1857,7 @@ Call `client_encryption_with_names.createDataKey()` with "azure:no_client_cert"
 masterKey:
 
 ```javascript
-{ 'keyVaultEndpoint': 'doesnotexist.local', 'keyName': 'foo' }
+{ 'keyVaultEndpoint': 'doesnotexist.invalid', 'keyName': 'foo' }
 ```
 
 Expect an error indicating TLS handshake failed.