ddl: let concurrent truncate on the same table depend on the previous one (#40501)

[ti-chi-bot]

This is an automated cherry-pick of #40501

Signed-off-by: wjhuang2016 huangwenjun1997@gmail.com

What problem does this PR solve?

Issue Number: close #40484

Problem Summary:

Suppose that we have:
DDL1: truncate table 1.
DDL2: truncate table 2.

Then DDL2 should depend on DDL1.

Since the table id changed, DDL2 is not dependent on DDL1 now.

What is changed and how it works?

For truncate table, its related ID including the old id and new id.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  As in the issue.
• 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:

• hawkingrei
• xiongjiwei

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.

[wjhuang2016]

/cherry-pick-invite

[ti-chi-bot]

@wjhuang2016 Please accept the invitation then you can push to the cherry-pick pull requests.
Comment with "/cherry-pick-invite" if the invitation is expired.
https://github.com/ti-chi-bot/tidb/invitations

[wjhuang2016]

/merge

[ti-chi-bot]

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

Commit hash: 130295c

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.