The validator expression used when creating a new collection should be validated according to the configured API version.

On sharded cluster with TrackUnshardedCollectionsUponCreation feature flag enabled, this validation is not happening. As a consequence, the user could successfully create a collection using a validator that violates the current API version configuration.
 
When this feature flag is enabled, we use the CreateCollectionCoordinator to create the collection that runs on a different thread/opCtx than the original request. Since the API version configuration is propagated through the opCtx when we use the coordinator we lose this information thus all the subsequent execution of the collection creation, including validation check will ignore the provided API version.

The goal of this ticket is to fix this issue and remove all the associated TODOs.