store: key ranges should be sorted in batch cop retry

[windtalker]

What problem does this PR solve?

Issue Number: close #44622

Problem Summary:

What is changed and how it works?

sort keyRanges when retry batch cop

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wshwsh12, XuHuaiyu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [XuHuaiyu,wshwsh12]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-06-13 09:41:31.038364637 +0000 UTC m=+78687.452968716: ☑️ agreed by XuHuaiyu.
• 2023-06-13 09:47:07.455738631 +0000 UTC m=+79023.870342709: ☑️ agreed by wshwsh12.

[windtalker]

/run-unit-test

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.3: #44632.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.4: #44634.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #44636.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #44638.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #44640.