DM loading NONCLUSTERED auto_increment and AUTO_ID_CACHE=1 table with lightning physical backend results in "duplicate entry"

[fubinzh]

What did you do?

Refer to: pingcap/tidb#46100
DM need update lightning version

What did you expect to see?

It should be OK for DM to load NONCLUSTERED auto_increment and AUTO_ID_CACHE=1 table with lightning physical backend.

What did you see instead?

After DM load data, later insert might report error "duplicate entry"

Versions of the cluster

DM version: v7.3.0

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)

[fubinzh]

/severity major

[fubinzh]

/label affects-7.1

[lichunzhu]

TiDB dependencies are already updated on master e4ac90b.
I use the original PR's pingcap/tidb#46171 integration test data to do a manual test and it works. Close this now.

[D3Hunter]

this pr #9642 already updated tidb dependency, and include the fix, 7.5 contains it

after #9954 cp to 7.1, 7.1 also contains the fix