*: fix 'duplicate entry' error when using br to restore AUTO_ID_CACHE=1 tables

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #44716, ref #38442

Problem Summary:

#39041 use separate allocator for row id and auto id.
That is some kind of compatibility-break, although it handle the backword-compatibility carefully in the tidb side, I still miss something in the br component.

When br backup a table with auto increment column, it get the row id allocator from the meta key. It should have used the auto increment id allocator after #39041

What is changed and how it works?

The auto increment meta key of a table with AUTO_ID_CACHE=1 option is a separated one, rather than the row ID meta key.

Check List

Tests

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

The steps descripted in #44716
I do think some integration test is necessory for this commit.

• 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

[tiancaiamao]

/retest-required

[xhebox]

FAILED ddl.TestAutoIncrementForceAutoIDCache

[bb7133]

PTAL @tangenta @3pointer

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leavrth, xhebox

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 [Leavrth,xhebox]

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-16 16:51:06.19100132 +0000 UTC m=+363662.605605400: ☑️ agreed by xhebox.
• 2023-06-16 16:54:35.677751204 +0000 UTC m=+363872.092355282: ✖️🔁 reset by xhebox.
• 2023-06-20 02:02:58.694374849 +0000 UTC m=+68344.095625283: ☑️ agreed by xhebox.
• 2023-06-20 02:07:25.470873206 +0000 UTC m=+68610.872123654: ☑️ agreed by Leavrth.

[tiancaiamao]

/merge

[tiancaiamao]

/retest unit-test

CI unit test fail on #44800

[ti-chi-bot]

@tiancaiamao: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-integration-br-test
• /test pull-integration-mysql-test
• /test unit-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/retest unit-test

CI unit test fail on #44800

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tiancaiamao]

/test unit-test

[ti-chi-bot]

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

[ti-chi-bot]

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

[tiancaiamao]

/run-cherry-picker