Don't create the first collection chunk on a primary drained shard

Once we mark a primary shard to drain via

db.runCommand( { removeShard: "my_primary_shard"})

the first chunk for new sharded collections will still be created on the primary drained shard and then it will be moved to another shard automatically.

We should be able to avoid this step and directly create the first chunk on another shard.