DRIVERS-3459: Use appName for hello failPoints in CMAP tests

source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-custom-maxConnecting-is-enforced.yml

@@ -12,11 +12,13 @@ failPoint:
     closeConnection: false
     blockConnection: true
     blockTimeMS: 500
+    appName: "cmap-format-tests"
 poolOptions:
   maxConnecting: 1
   # gives opportunity for the checkout in thread2 to establish a new connection, which it must not do until thread1 establishes one
   maxPoolSize: 2
   waitQueueTimeoutMS: 5000
+  appName: "cmap-format-tests"
 operations:
   - name: ready
   # thread1 exists to consume the single permit to open a connection,

source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-is-enforced.yml

@@ -14,9 +14,11 @@ failPoint:
     closeConnection: false
     blockConnection: true
     blockTimeMS: 800
+    appName: "cmap-format-tests"
 poolOptions:
   maxPoolSize: 10
   waitQueueTimeoutMS: 5000
+  appName: "cmap-format-tests"
 operations:
   - name: ready
   # start 3 threads

source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-timeout.yml

@@ -14,12 +14,14 @@ failPoint:
     closeConnection: false
     blockConnection: true
     blockTimeMS: 750
+    appName: "cmap-format-tests"
 poolOptions:
   maxPoolSize: 10
   # Drivers that limit connection establishment by waitQueueTimeoutMS may skip
   # this test. While waitQueueTimeoutMS is technically not supposed to limit establishment time,
   # it will soon be deprecated, so it is easier for those drivers to just skip this test.
   waitQueueTimeoutMS: 50
+  appName: "cmap-format-tests"
 operations:
   - name: ready
   # start creating two connections simultaneously.

source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-minPoolSize-connection-maxConnecting.yml

@@ -13,12 +13,14 @@ failPoint:
     closeConnection: false
     blockConnection: true
     blockTimeMS: 500
+    appName: "cmap-format-tests"
 poolOptions:
   # allows both thread1 and the background thread to start opening connections concurrently
   minPoolSize: 2
   # gives opportunity for the checkout in thread2 to open a new connection, which it must not do nonetheless
   maxPoolSize: 3
   waitQueueTimeoutMS: 5000
+  appName: "cmap-format-tests"
 operations:
   - name: ready
   # thread1 exists to hold on one of the two permits to open a connection (the other one is initially held by the background thread),

source/connection-monitoring-and-pooling/tests/cmap-format/pool-checkout-returned-connection-maxConnecting.yml

@@ -14,10 +14,12 @@ failPoint:
     closeConnection: false
     blockConnection: true
     blockTimeMS: 750
+    appName: "cmap-format-tests"
 poolOptions:
   maxConnecting: 2
   maxPoolSize: 10
   waitQueueTimeoutMS: 5000
+  appName: "cmap-format-tests"
 operations:
   - name: ready
   # check out a connection and hold on to it.

source/connection-monitoring-and-pooling/tests/cmap-format/pool-clear-interrupting-pending-connections.yml

@@ -12,8 +12,10 @@ failPoint:
     closeConnection: false
     blockConnection: true
     blockTimeMS: 10000
+    appName: "cmap-format-tests"
 poolOptions:
   minPoolSize: 0
+  appName: "cmap-format-tests"
 operations:
   - name: ready
   - name: start