import: fix dup-detect failure on index data

[dsdashun]

What problem does this PR solve?

Issue Number: close #39476

Problem Summary:

What is changed and how it works?

Pass the index info when constructing a dup-detect task for index data. Otherwise the task will be treated as a record data dup-detect task.

Check List

Tests

• Unit test
• Integration test (covered in lightning_duplicate_detection)
• 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
• Ehco1996

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.

[dsdashun]

/run-integration-br-test

[Ehco1996]

LGTM after seen this #39476 (comment)

[dsdashun]

Integration BR test failed at br_foreign_key. All Lightning integration tests have passed:
https://ci.pingcap.net/blue/organizations/jenkins/br_ghpr_unit_and_integration_test/detail/br_ghpr_unit_and_integration_test/14283/pipeline

[dsdashun]

/merge

[ti-chi-bot]

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

Commit hash: 49f6045

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [2] 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	🟥 failed 1, success 27, total 28	6 min 1 sec	New failing
idc-jenkins-ci-tidb/sqllogic-test-1	🟥 failed 1, success 25, total 26	5 min 5 sec	New failing
idc-jenkins-ci/integration-cdc-test	🔴 failed 1, success 39, total 40	25 min	Existing failure
idc-jenkins-ci-tidb/integration-common-test	🔴 failed 2, success 15, total 17	22 min	Existing failure
idc-jenkins-ci-tidb/common-test	🔴 failed 1, success 10, total 11	11 min	Existing failure
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	10 min	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	6 min 12 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	4 min 30 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 54 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed