ctl: clone tls config to avoid reusing connection

[HuSharp]

What problem does this PR solve?

Issue Number: Close #7739

What is changed and how does it work?

• There is a read goroutine inside http transport that detects the closure of the socket. When another request is made before the readLoop actually detects the closure, the socket closes and an EOF is read.
• When they have the same tls they will shared connection
• release 7.6 does update member at startup.
• Since get stores are slow, update member is done when the request is sent and not yet returned.
• Then the member returns faster and sends the request to readloop to read the return and then closes the socket, and stores encounters an eof.

can check error log
update member

store url

they are using URL in the same time

Check List

Tests

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

Release note

ctl: clone tls config to avoid reusing connection

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• JmPotato
• lhy1024

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.

[HuSharp]

/check-issue-triage-complete

[codecov]

Codecov Report

Merging #7740 (d1285fa) into master (649cc8a) will increase coverage by 0.12%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7740      +/-   ##
==========================================
+ Coverage   73.68%   73.80%   +0.12%     
==========================================
  Files         429      429              
  Lines       47591    47591              
==========================================
+ Hits        35068    35126      +58     
+ Misses       9520     9472      -48     
+ Partials     3003     2993      -10     

Flag	Coverage Δ
unittests	73.80% <ø> (+0.12%)	⬆️

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

[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: d1285fa

[ti-chi-bot]

/cherry-pick release-7.6

[ti-chi-bot]

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

[ti-chi-bot]

@ti-chi-bot: new pull request could not be created: failed to create pull request against tikv/pd#release-7.6 from head ti-chi-bot:cherry-pick-7740-to-release-7.6: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-7740-to-release-7.6."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-7.6

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.