MDEV-34998: master can stop responding after cluster vote to evict a node

Additional corrections: there is a natural race between closing connection
to cluster in case of applying error and finishing the IST and sometimes
IST finishes and tries to send JOIN message over a closed connection.
This does not affect the correctness of the test or node behavior.
Added error message suppression.

Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>

mysql-test/suite/galera/r/galera_vote_during_ist.result

@@ -108,3 +108,5 @@ CALL mtr.add_suppression("BF applier thread=.+ failed to open_and_lock_tables fo
 CALL mtr.add_suppression("Event 3 Write_rows_v1 apply failed: 1146");
 CALL mtr.add_suppression("Inconsistency detected: Failed on preordered");
 CALL mtr.add_suppression("Failed to apply write set");
+CALL mtr.add_suppression("Sending JOIN failed: -103");
+CALL mtr.add_suppression("Failed to JOIN the cluster after SST");

mysql-test/suite/galera/t/galera_vote_during_ist.test

@@ -159,5 +159,7 @@ CALL mtr.add_suppression("BF applier thread=.+ failed to open_and_lock_tables fo
 CALL mtr.add_suppression("Event 3 Write_rows_v1 apply failed: 1146");
 CALL mtr.add_suppression("Inconsistency detected: Failed on preordered");
 CALL mtr.add_suppression("Failed to apply write set");
+CALL mtr.add_suppression("Sending JOIN failed: -103");
+CALL mtr.add_suppression("Failed to JOIN the cluster after SST");
 
 --source ../include/auto_increment_offset_restore.inc