ddl: postpone cleaning placement rules to gc-worker

[AilinKid]

What problem does this PR solve?

Issue Number: close #28686

Problem Summary:

What is changed and how it works?

What's Changed:
1: remove the instant notification of cleaning placement rules when dropping table in the ddl workers.
2: make gc worker clean all the placement rules for both table and partitions (since it's idempotent, doing it for every partition range is ok)

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

Test
case 1: non-partition table
tiup playground v5.0.1 --tiflash 0  --kv 2 --db 1
create table t(a int) constraints="[-region=hdd]"
drop table t
http://127.0.0.1:2379/pd/api/v1/config/placement-rule     // check placement rules for table t is cleaned after gc_life_time

case 1: partition table
create table t2(a int) constraints="[-region=ssd]" partition by range(a) (PARTITION p0 VALUES LESS THAN (100) constraints="[-region=hdd]");
drop table t
http://127.0.0.1:2379/pd/api/v1/config/placement-rule     // check placement rules for table t2 is cleaned after gc_life_time

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• djshow832
• xhebox

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.

[sre-bot]

Please follow PR Title Format:

• pkg [, pkg2, pkg3]: what is changed

Or if the count of mainly changed packages are more than 3, use

• *: what is changed

After you have format title, you can leave a comment /run-check_title to recheck it

[AilinKid]

/run-check_dev_2

[lcwangchao]

I think we should add some comments here about why we not drop rule bundles here and postpone it to gc_worker.

[AilinKid]

added:
Placement rules cannot be removed immediately after drop table / truncate table, because the tables can be flashed back or recovered.

[lcwangchao]

LGTM. but I'm not very familiar with gc_worker. May be you can ask another one to review it again? @AilinKid

[AilinKid]

LGTM. but I'm not very familiar with gc_worker. May be you can ask another one to review it again? @AilinKid

@djshow832

[djshow832]

/merge

[ti-chi-bot]

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

Commit hash: b48dc9f

[ti-chi-bot]

@AilinKid: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

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.