[DNM]GC: Support keyspace level GC

[ystaticy]

What problem does this PR solve?

Issue Number: ref #51593

Problem Summary:

What changed and how does it work?

Check List

Tests

• Manual test (add detailed scripts or steps below)

1. set keyspace level gc when create Keyspace:
   1.1. create new keyspace with keyspace level gc:

   curl -H "Content-Type: application/json" -X POST -d \
   '{
       "name": "ks1",
       "config": {
           "gc_management_type": "keyspace_level_gc"
       }
   }' "http://127.0.0.1:2379/pd/api/v2/keyspaces"
   

   Get keyspace meta:

   curl "http://127.0.0.1:2379/pd/api/v2/keyspaces/ks1"
   {
       "id": 1,
       "name": "ks1",
       "state": "ENABLED",
       "created_at": 1712126594,
       "state_changed_at": 1712126594,
       "config": {
           "gc_management_type": "keyspace_level_gc"
       }
   }
   

   1.2. Start TiDB and check the etcd key
   You can see that the ETCD key of safe point and min start ts in pd is separated by Keyspace:

   1.minstartts
   /keyspaces/tidb/1/tidb/server/minstartts/1fbc785c-dada-4152-a2e7-f0534a386e6e
   
   2.saved safe point
   /keyspaces/tidb/1/tidb/store/gcworker/saved_safe_point
   
   4.gc safe point 
   /pd/7340112560849754553/keyspaces/gc_safe_point/00000001
   
   5.service safe point 
   /pd/7340112560849754553/keyspaces/service_safe_point/00000001/gc_worker
   

2. Check that PD's ETCD key remains in its original format without Keyspace set:

   1. minstartts
   /tidb/server/minstartts/f8545873-a97a-4aaf-be10-53633490b339
   
   2. saved safe point 
   /tidb/store/gcworker/saved_safe_point
   
   3. gc safe point
   /pd/7340566695597925295/gc/safe_point
   
   4. service safe point 
   /pd/7340566695597925295/gc/safe_point/service/gc_worker
   

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.

Support TiDB server with different keyspace to advance GC safe point separately

[tiprow]

Hi @ystaticy. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Attention: Patch coverage is 42.50000% with 161 lines in your changes missing coverage. Please review.

Project coverage is 74.7151%. Comparing base (0374ae2) to head (a29b940).
Report is 1 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51300        +/-   ##
================================================
+ Coverage   72.8615%   74.7151%   +1.8535%     
================================================
  Files          1677       1722        +45     
  Lines        464138     472456      +8318     
================================================
+ Hits         338178     352996     +14818     
+ Misses       105082      97261      -7821     
- Partials      20878      22199      +1321     

Flag	Coverage Δ
integration	49.1981% <3.2142%> (?)
unit	72.2169% <42.5000%> (-0.0366%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	61.1606% <ø> (+15.4570%)	⬆️

[ystaticy]

/test check-dev2

[tiprow]

@ystaticy: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

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]

@AmoebaProtozoa: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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.

[ystaticy]

/test check-dev

[ti-chi-bot]

@baiyuqing: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AmoebaProtozoa, baiyuqing
Once this PR has been reviewed and has the lgtm label, please assign tangenta for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• pkg/domain/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[baiyuqing]

LGTM