With auto-bootstrapping, it is not guaranteed that once `new ShardingTest` returns, the host field for the config shard's shard entry will contain all of the members of the replica set.

This is because with auto-bootstrapping, the host field will initially only contain the auto-bootstrapped node. The shard entry will only get updated to contain all of the nodes in the replica set when a mongos notices the config server replica set's other members (which can happen after `new ShardingTest` returns).

This is not a issue without auto-bootstrapping because the config shard is only created after the user has fully initiated their replica set.