Before v6.0, moveChunk operations issued by users where ending up calling into the configsvr_client that was issuing runCommand with idempotent retry policy, resulting in indefinitely retrying the command in case of retriable errors.

With the introduction of the moveRange path, the semantic has been involuntarily changed to a retry with fixed retry attempts both for moveRange and for moveChunk.

Purpose of this ticket is to reintroduce the original retry logic.