lightning: support detect duplicate keys on specific index ID

[tangenta]

What problem does this PR solve?

Issue Number: ref #35983

Problem Summary:

To support adding index through lightning, an essential feature is to detect the duplicate key for the unique indexes.

What is changed and how it works?

This PR adds support for Backend to collect duplicate keys on a specific index ID.

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:

• D3Hunter
• gozssky

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.

[D3Hunter]

/run-integration-br-test

[tangenta]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 6088c5d

[ti-chi-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/67d3cda0c116918551a9d06995536b993bd14494

[ti-chi-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/67d3cda0c116918551a9d06995536b993bd14494

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! [2] CI still failing after this pr merged.
These failed integration tests don't seem to be introduced by the current PR.

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/common-test	🔴 failed 1, success 10, total 11	13 min	Existing failure
idc-jenkins-ci-tidb/integration-common-test	🔴 failed 1, success 16, total 17	11 min	Existing failure
idc-jenkins-ci/integration-cdc-test	🟢 all 36 tests passed	29 min	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	5 min 14 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	4 min 44 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	4 min 24 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	3 min 25 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 14 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed