ShardingDDLCoordinator's should join an existing operation if all the options match. Reshard collection coordinator (which moveCollection uses) is a sharding DDL coordinator and joins an existing operation correctly for reshardCollection. But since we added a call to register the collection in the catalog for moveCollection, a second moveCollection command will get blocked on the createCollection request since it will wait to acquire the locks that the first operation is holding since they're two different DDLs (create and reshard).

We should skip the call to track the collection if it's already tracked for a moveCollection request.