After SERVER-81189 in order to guarantee the api version check for {create ... }, the api version information has been forcefully attached to the shardsvrCreateCollection command. Those information are ignored as  shardsvrCreateCollection does not require api version check. Afterwards, those information are attached to the {create..} run by a direct client connection.

However, after SERVER-81190 some {create .. } will run by the CreateCollection coordinator which spawns a new operation context and those information are lost. 

The goal of this ticket is to guarantee the api version check.

Important: the api check is usually performed right at the beginning of the entry point before any other error can be thrown. Once reached the coordinator, other errors could be thrown before due to previous checks. A possible solution for this ticket could be to directly work on the entry point and make sure this check is performed there.