newly sharded collection requires config info reload on the mongod

If we shard a collection with one mongos, the mongod will not know about the change until a setShardVersion command comes in. Since other mongoses do not know about the change, they may never send another setShardVersion command if they don't re-establish connections.

This can cause mongoses not to split, if the shard command comes from one mongos which then is not used to insert the data.