ddl: fix the placement behavior when drop/truncate partitions (#44129)

[ti-chi-bot]

This is an automated cherry-pick of #44129

What problem does this PR solve?

Issue Number: close #44116

What is changed and how it works?

When dropping/truncating a partition, this PR will:

• reset the table's placement group with the new meta. After that, the dropped partition id not in the table's placement group.
• create a new placement group by dropped partition id with the old rules to wait for GC to delete it.

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.

ddl: fix the placement behavior when drop/truncate partitions

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hawkingrei
• lcwangchao

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.

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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 kubernetes/test-infra repository.

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	223dd7a	link	true	/test build
idc-jenkins-ci-tidb/check_dev_2	223dd7a	link	true	/test check-dev2
idc-jenkins-ci-tidb/mysql-test	223dd7a	link	true	/test mysql-test
idc-jenkins-ci-tidb/unit-test	223dd7a	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev	223dd7a	link	true	/test check-dev

Full PR test history. Your PR dashboard.

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 kubernetes/test-infra repository. I understand the commands that are listed here.

[lcwangchao]

It will be merged to one cherry-pick PR #44062