ShardingTest in v3.2 defaults to disabling the balancer. There's no need to call stopBalancer when it is already disabled.

This is causing a failure in the continuous step down suite, because stopBalancer does a write and cannot be retried when interrupted by a config primary step down.