autoid_service: support keyspace has own auto id leader

[ystaticy]

What problem does this PR solve?

Issue Number: ref #46286

Problem Summary:

What is changed and how it works?

Add keyspace prefix to the etcd path of the autoid leader for each keyspace.

Check List

Tests

• Manual test (add detailed scripts or steps below)
  Every keyspace has its own auto id leader.
  keyspace-name="ks1"

["get owner"] [keyspaceName=ks1] ["owner info"="[autoid] tidb/autoid/leader ownerManager 127.0.0.1:40573"] ["owner key"=tidb/autoid/leader/2d808a2698157607] [ownerID=127.0.0.1:40573] [op=none]

keyspace-name="ks2"

["get owner"] [keyspaceName=ks2] ["owner info"="[autoid] tidb/autoid/leader ownerManager 127.0.0.1:40583"] ["owner key"=tidb/autoid/leader/7618a2698157738] [ownerID=127.0.0.1:40583] [op=none]

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.

Support keyspace has own auto id leader.

[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

Merging #46285 (eecc3bd) into master (9411e82) will decrease coverage by 0.0638%.
Report is 42 commits behind head on master.
The diff coverage is 0.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #46285        +/-   ##
================================================
- Coverage   73.3854%   73.3217%   -0.0638%     
================================================
  Files          1285       1319        +34     
  Lines        394836     407005     +12169     
================================================
+ Hits         289752     298423      +8671     
- Misses        86633      90017      +3384     
- Partials      18451      18565       +114     

Flag	Coverage Δ
integration	26.3857% <0.0000%> (?)
unit	73.9895% <0.0000%> (+0.6041%)	⬆️

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

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	85.0810% <ø> (+0.0143%)	⬆️
br	48.3551% <ø> (-3.8647%)	⬇️

[ystaticy]

/test mysql-test

[tiprow]

@ystaticy: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test mysql-test

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.

[tiancaiamao]

/ok-to-test

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, tiancaiamao

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tangenta,tiancaiamao]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-08-24 08:28:13.475368874 +0000 UTC m=+1397258.024384846: ☑️ agreed by tangenta.
• 2023-08-24 08:28:37.399819383 +0000 UTC m=+1397281.948835369: ☑️ agreed by tiancaiamao.

[wuhuizuo]

/retest

[ystaticy]

/retest