Similarly to what we do in the recoverable critical section, the goal of this ticket is to extend the ShardingMigrationCriticalSection to keep track of which operation is currently using the CS.

As a secondary goal, we should implement its methods in such a way that acquiring the same CS twice it is not an error if the reason is the same.