Currently, the shardVersion recovery task is scheduled on a fixed-size executor. What is worse, the "opportunistic recovery" task, which we spawn on step-up, runs on the same fixed-size executor and does a blocking wait for the shardVersion recovery to complete, which is this is deadlock-prone.

The shardVersion recovery task must instead use the sharding unilimited size executor.