AppTelemetryTests: Catch connection error less restrictively

Sometimes rather than BrokenPipeError we can see a ConnectionResetError

disconnect_on_disable_test...                                  failed
  ConnectionResetError: [Errno 104] Connection reset by peer

(seen in:
 https://cv.jenkins.couchbase.com/job/ns-server-cluster-tests/14389/)

Until we support the proper websocket close handshake, make the check
less restrictive, to avoid intermittant test failures.

Change-Id: Ie6cb6e34f709300d45d114491bc10887887d8567
Reviewed-on: https://review.couchbase.org/c/ns_server/+/224049
Tested-by: Peter Searby <[email protected]>
Reviewed-by: Timofey Barmin <[email protected]>

Author: Peter-Searby

cluster_tests/testsets/app_telemetry_tests.py

@@ -175,7 +175,7 @@ def disconnect_on_disable_test(self):
                 try:
                     frame = conn.get_next_frame()
                     testlib.assert_eq(frame.opcode, Opcode.CLOSE)
-                except BrokenPipeError:
+                except ConnectionError:
                     # See MB-65238. The websocket may be closed before receiving
                     # the response to the CLOSE message, which is sent in
                     # WebsocketConnection._get_and_send_data