tests: fix auth warning assertion for --smp 2 compatibility

The test_can_connect_with_sslauth test asserted exact equality between
auth warning count and ReadyMessage count. With --smp 2, shard-aware
connections produce additional ReadyMessages, breaking the equality.

Drop the exact equality check and keep only the >= 4 lower bound, which
validates the test's actual intent: warnings are issued when auth is
configured but the server does not challenge.

Author: mykaul

tests/integration/standard/test_cluster.py

@@ -720,10 +720,13 @@ def _warning_are_issued_when_auth(self, auth_provider):
                 session = cluster.connect()
                 assert session.execute("SELECT * from system.local WHERE key='local'") is not None
 
-            # Three conenctions to nodes plus the control connection
+            # Verify that auth warnings are issued for connections where
+            # auth is configured but the server does not send a challenge.
+            # At minimum: 3 nodes + 1 control connection = 4 warnings.
+            # With --smp >= 2, additional shard-aware connections may also
+            # produce warnings, so we only assert a lower bound.
             auth_warning = mock_handler.get_message_count('warning', "An authentication challenge was not sent")
             assert auth_warning >= 4
-            assert auth_warning == mock_handler.get_message_count("debug", "Got ReadyMessage on new connection")
 
     def _wait_for_all_shard_connections(self, cluster, timeout=30):
         """Wait until all shard-aware connections are fully established."""