*: share etcd client from domain for autoid allocator (#46647)

[ti-chi-bot]

This is an automated cherry-pick of #46647

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

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-7.1@eac9cd0). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.1     #48308   +/-   ##
================================================
  Coverage               ?   73.4077%           
================================================
  Files                  ?       1206           
  Lines                  ?     377960           
  Branches               ?          0           
================================================
  Hits                   ?     277452           
  Misses                 ?      82800           
  Partials               ?      17708           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 [lcwangchao,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]

[LGTM Timeline notifier]

Timeline:

• 2023-12-07 02:59:34.222708685 +0000 UTC m=+1669202.887934874: ☑️ agreed by lcwangchao.
• 2023-12-07 07:40:27.656366838 +0000 UTC m=+1686056.321593034: ☑️ agreed by tangenta.

[tiancaiamao]

#48891 contains changes of this one, so this one is not need any more.

[ti-chi-bot]

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

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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.