The clusterAllCollectionsByDefault failpoint is only considered by a local create command. Therefore, although a shardingCollection operation creates a clustered collection when clusterAllCollectionsByDefault failpoint is enabled, it's unaware of the decision to cluster the collection by default.

The aim of this ticket is to update the collection options according to the `clusterAllCollectionsByDefault` failpoint value at an earlier stage.