For the concurrency stepdown suites, if the donor shard's primary steps down right after sending _recvChunkStart to the recipient and its primary in the next term aborts the migration during migration recovery and immediately starts another migration, when the recipient sends _migrationClone for the aborted migration to the latest donor's shard primary, the command will fail the session id validation. This would cause the moveChunk to fail with OperationFailed with the error message "Requested migration session id ... does not match active session id ..." since there is other active migration. Therefore, we need to make the moveChunk helper also retry the command on OperationFailed error with that error message.