The explicit create command on mongos was made to call _configsvrCreateCollection when we added the implicit collection creation loop through the config server under SERVER-32291.

To make it easier for the storage execution team to implement DDL in transactions, we should revert the create command behavior back to what it was before. At the moment, they are having trouble because the client's lsid, txnNumber is being propagated on _configsvrCreateCollection, which doesn't play well with the config server upconverting default writeConcern to majority, because writeConcern is not allowed on transaction statements besides commitTransaction.