*: upgrade etcd to v3.4.30

[JmPotato]

What problem does this PR solve?

Issue Number: close #7904, ref #5520.

• Release note: https://github.com/etcd-io/etcd/releases/tag/v3.4.30
• Code changes are caused by etcd-io/etcd@6de105e.

What is changed and how does it work?

Upgrade etcd to v3.4.30 and adopt the latest code changes.

Check List

Tests

• Unit test
• Integration test

Release note

Upgrade etcd to v3.4.30 to adopt the security patch.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• HuSharp
• rleungx

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.

[codecov]

Codecov Report

Merging #7884 (635d4ac) into master (32bba44) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7884      +/-   ##
==========================================
- Coverage   73.49%   73.42%   -0.07%     
==========================================
  Files         434      434              
  Lines       48035    48035              
==========================================
- Hits        35302    35272      -30     
- Misses       9690     9705      +15     
- Partials     3043     3058      +15     

Flag	Coverage Δ
unittests	73.42% <100.00%> (-0.07%)	⬇️

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

[wuhuizuo]

/hold

It needs to be upgrade to "v3.4.30".

@JmPotato

[wuhuizuo]

/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

[ti-chi-bot]

@wuhuizuo: once the present PR merges, I will cherry-pick it on top of release-6.1/release-6.5/release-7.1/release-7.5 in the new PR and assign it to you.

In response to this:

/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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 ti-community-infra/tichi repository.

[wuhuizuo]

/cherry-pick release-7.5 /cherry-pick release-7.1 /cherry-pick release-6.5 /cherry-pick release-6.1

cc @JmPotato

[JmPotato]

/unhold

[JmPotato]

/merge

[ti-chi-bot]

@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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

Commit hash: 9c0ae62

[JmPotato]

/merge

[ti-chi-bot]

@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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

Commit hash: 635d4ac

[ti-chi-bot]

@wuhuizuo: new pull request created to branch release-6.5: #7886.

In response to this:

/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@wuhuizuo: new pull request created to branch release-6.1: #7887.

In response to this:

/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@wuhuizuo: new pull request created to branch release-7.5: #7888.

In response to this:

/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@wuhuizuo: new pull request created to branch release-7.1: #7889.

In response to this:

/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

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 ti-community-infra/tichi repository.