Adjustmen of expected error handling\ignorance in SCT

[timtimb0t]

https://argus.scylladb.com/tests/scylla-cluster-tests/d8bdb54c-02b7-4267-9a8e-3d2cdd5191c3

there are few nemeses that generate closed connection type errors during runtime:

• disrupt_destroy_data_then_rebuild
• disrupt_destroy_data_then_repair

Such errors look like:

!ERR | scylla[1311]:  [shard  0: gms] raft_topology - drain rpc failed, proceed to fence old writes: std::runtime_error (raft topology: exec_global_command(barrier_and_drain) failed with seastar::rpc::closed_error (connection is closed))

such an errors are expected for these nemeses and maybe ignored by SCT to avoid redundant error messages in argus.

Here is the issue with explanation of the nature of such errors
#9031 (comment)

[timtimb0t]

closed due to its basically dup of:
#9031