The config server's manual move chunk internal call _configsvrMoveChunk is intended to be idempotent in the absence of other metadata changing activity on the system and the continuous stepdown suite relies on this behaviour.

However, in the case where waitForDelete is specified and the move chunk operation on the shard is already at the stage where cleanup happens, _configsvrMoveChunk may report a retried operation as successful before the cleanup has completed.

This causes tests, which rely on the range cleanup to complete to fail when run under the continuous config stepdown suite.