Currently, the cluster_remove_shard_cmd only verifies the command-level status. To be consistent with the cluster_transition_to_dedicated_config_server command, as part of this ticket, we should also assert on the write concern status. To this aim, we should use the {{Shard::CommandResponse::getEffectiveStatus, }} to evaluate both.