In SERVER-67633 we made that create collection operations serialize with the collection critical section if present. In particular in order to achieve so we made that the mongos always add shard version UNSHARDED to the create collection request that is being forwarded to the shard.
The problem is that we forget about collection creation path that can happen during aggregation execution.

This means that collection creation that happens as part of aggregation execution will ignore the critical section

The goal of this ticket is to:

• Fix the executeCommandOnDatabasePrimary. The cmdObjWithShardVersion variable is never used.
• Ensure all creation path use the executeCommandOnDatabasePrimary wrapper and properly attach the shard version UNSHARDED.