*: share etcd client from domain for autoid allocator

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #46324

Problem Summary:

The autoid allocate service need a etcd client, we can create one and close it after use.
But every time infoschema reload, we need to create one...
A better solution is to share the etcd client in domain.Domain (also ddl.DDL)

What is changed and how it works?

Refactor the auto id parameter from kv.Store to autoid.Requirement
The autoid.Requirement now consists of a kv.Store and a clientv3.Client...
This change affect quite a lot packages, especially tools packages.

Check List

Tests

This is a code refactor so all the old tests should not be break.

• 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.

None

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @tiancaiamao. 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.

[tiancaiamao]

/ok-to-test

[tiancaiamao]

/ok-to-test

[codecov]

Codecov Report

Merging #46647 (dc56cb0) into master (028d7b8) will increase coverage by 1.2924%.
Report is 28 commits behind head on master.
The diff coverage is 55.7692%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #46647        +/-   ##
================================================
+ Coverage   71.5384%   72.8309%   +1.2924%     
================================================
  Files          1402       1425        +23     
  Lines        406159     412790      +6631     
================================================
+ Hits         290560     300639     +10079     
+ Misses        95775      93251      -2524     
+ Partials      19824      18900       -924     

Flag	Coverage Δ
integration	43.1580% <45.0000%> (?)
unit	71.4626% <53.8461%> (-0.0759%)	⬇️

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

Components	Coverage Δ
dumpling	53.9874% <ø> (ø)
parser	∅ <ø> (∅)
br	48.6628% <40.6250%> (-4.2323%)	⬇️

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-11-03 02:50:14.966118871 +0000 UTC m=+3180612.553229000: ☑️ agreed by lcwangchao.
• 2023-11-06 01:16:25.003878991 +0000 UTC m=+3434182.590989140: ☑️ agreed by GMHDBJD.

[3pointer]

br part LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, GMHDBJD, lcwangchao, tangenta

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 [3pointer,GMHDBJD,lcwangchao,tangenta]
• br/OWNERS [3pointer]
• br/pkg/lightning/OWNERS [GMHDBJD]
• pkg/ddl/OWNERS [tangenta]
• pkg/disttask/OWNERS [GMHDBJD,tangenta]
• pkg/domain/OWNERS [GMHDBJD,tangenta]
• pkg/infoschema/OWNERS [GMHDBJD,tangenta]
• pkg/meta/OWNERS [GMHDBJD,tangenta]

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]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-tests-checked label, please finished the tests then check the finished items in description.

For example:

Tests

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

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}

[tiancaiamao]

/test mysql-test

[tiprow]

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

• /test tiprow_fast_test

Use /test all to run all jobs.

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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #48308.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #48309.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #48310.