lightning: fix incorrect _tidb_rowid allocator value after import for table with AUTO_ID_CACHE=1 (#46171)

[ti-chi-bot]

This is an automated cherry-pick of #46171

What problem does this PR solve?

Issue Number: close #46100

Problem Summary:

since TiDB v6.5.0, we have separate id allocator for _tidb_rowid and auto_increment id when AUTO_ID_CACHE=1, see #39041, and ALTER TABLE x AUTO_INCREMENT=x only works on the allocator of auto_increment in this case, but if the table have implicit _tidb_rowid, we should update it's base too to make sure new insert works, else it will report duplicate entry

What is changed and how it works?

• rebase on both allocators when needed after import

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

[D3Hunter]

/lgtm

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/lgtm

[ti-chi-bot]

@D3Hunter: Your lgtm message is repeated, so it is ignored.

In response to this:

/lgtm

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, lance6716

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 [D3Hunter,lance6716]

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-08-18 02:40:52.565650497 +0000 UTC m=+858017.114666471: ☑️ agreed by D3Hunter.
• 2023-08-18 03:08:40.419509518 +0000 UTC m=+859684.968525505: ☑️ agreed by lance6716.

[D3Hunter]

/retest

[D3Hunter]

/hold

wait ci

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[Ivy-YinSu]

/run-integration-br-test

[Ivy-YinSu]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-6.5@07c1326). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #46183   +/-   ##
================================================
  Coverage               ?   73.6722%           
================================================
  Files                  ?       1084           
  Lines                  ?     347945           
  Branches               ?          0           
================================================
  Hits                   ?     256339           
  Misses                 ?      75155           
  Partials               ?      16451           

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/run-integration-br-test

[D3Hunter]

/retest

[D3Hunter]

lightning ci pass, some br cases are so unstable, we won't wait them, as this pr only change lightning part

https://ci.pingcap.net/blue/organizations/jenkins/br_ghpr_unit_and_integration_test/detail/br_ghpr_unit_and_integration_test/16112/pipeline/117

those cases're run locally, success
lightning_alter_random
lightning_auto_columns
lightning_auto_random_default

[D3Hunter]

/unhold