*: separate auto_increment ID allocator from _tidb_rowid allocator when AUTO_ID_CACHE=1

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #982

Problem Summary:

In the past, both _row_id and auto_increment_id share the same allocator, so the behaviour is not compatible with MySQL.
We try to solve it in the past #20708, but that increase the risk of been incompatible to the old TiDB. So we mark it as won't fix. (I have to mention that clustered index relieve some of the cases, and clustered index is enabled by default now, through it does not solve all the issues)

Now we are trying to introduce a MySQL-compatible mode #38449, this is a good time to fix the behaviour. With table option AUTO_ID_CACHE 1, the new implementation is used.

What is changed and how it works?

Seperate auto_increment ID allocator from _tidb_rowid allocator oinly when table option AUTO_ID_CACHE=1 is used.

1. create table ... AUTO_ID_CACHE 1 ... decides whether to use SepAutoInc by checking AutoIdCache and Version in model.TableInfo
2. Correct the call side of RowID and AutoIncrementID
3. If Allocators.Get() find SepAutoInc is not set, it changes AutoIncrementID to RowID; otherwise AutoIncrementID is used

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]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• tangenta
• xhebox

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[tiancaiamao]

PTAL @bb7133 @tangenta

[tiancaiamao]

/run-unit-test

[tiancaiamao]

/run-unit-test

[tiancaiamao]

/run-unit-test

[wuhuizuo]

/run-check-dev-2
/run-mysql-test

[tiancaiamao]

/run-check_dev_2
/run-unit-test

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [1] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/sqllogic-test-2	🟥	1 min 6 sec	New failing
idc-jenkins-ci-tidb/integration-ddl-test	🔴 failed 2, success 4, total 6	5 min 15 sec	Existing failure
idc-jenkins-ci/integration-cdc-test	✅ all 40 tests passed	20 min	Fixed
idc-jenkins-ci-tidb/common-test	✅ all 11 tests passed	10 min	Fixed
idc-jenkins-ci-tidb/sqllogic-test-1	✅ all 26 tests passed	5 min 32 sec	Fixed
idc-jenkins-ci-tidb/integration-common-test	🟢 all 17 tests passed	15 min	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	6 min 21 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	6 min 2 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	2 min 51 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed