meta/autoid: enable etcd client auto sync for autoid service

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #42643

ref #9575, ref #33908

Problem Summary:

When the pd server change, the corresponding etcd address should be auto-refresh on the client side.

What is changed and how it works?

While it is easy to just add back the option AutoSyncInterval: 30 * time.Second in, I think a bigger issue is why do we need to have 4 different etcd clients rather than sharing the same one with all the correct config 🤷

Because 1. tidb repo is too big, and it's not designed to be used as a lib. (this applies to all tidb/util/xxx), so the etcd client utility in the tidb repo is not a good place to be shared by other repos (tools / binlog ...)
2. For autoid service, it's a indenpendent component, the code is put to the tidb repo though. So this case is similiar to tools etc.
It should have shared the same etcd client instance, but it's not available when the server startup.

Maybe we can maintain a pingcap/etcdutil lib to solve the " 4 different etcd clients" issue

Check List

Tests

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

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hawkingrei
• zimulala

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.

[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

[zimulala]

LGTM

[hawkingrei]

/merge

[ti-chi-bot]

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

Commit hash: 8150e70

[hawkingrei]

/merge

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[tiancaiamao]

Affect tidb v6.4.0 above