deps, lightning: update the PD HTTP client to refine the retry logic

[JmPotato]

What problem does this PR solve?

Issue Number: ref #35319, close tikv/pd#7673.

Problem Summary:

Lightning updated the PD HTTP client but did not keep the same retry logic as before.

What changed and how does it work?

• Update the PD HTTP client to adopt the latest retry logic.
• Add a backoffer to the Lightning PD HTTP client to keep the same retry interval and frequency as before.

Check List

Tests

• Unit test
• Integration test

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[JmPotato]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[codecov]

Codecov Report

Merging #50225 (0df1377) into master (136ae46) will decrease coverage by 14.3789%.
Report is 2 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #50225         +/-   ##
=================================================
- Coverage   70.0612%   55.6823%   -14.3789%     
=================================================
  Files          1441       1548        +107     
  Lines        419730     582355     +162625     
=================================================
+ Hits         294068     324269      +30201     
- Misses       105349     235420     +130071     
- Partials      20313      22666       +2353     

Flag	Coverage Δ
integration	36.4322% <85.7142%> (?)
unit	70.0276% <28.5714%> (-0.0337%)	⬇️

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

Components	Coverage Δ
dumpling	54.0269% <ø> (ø)
parser	∅ <ø> (∅)
br	55.2547% <100.0000%> (+5.5677%)	⬆️

[JmPotato]

/cc @hawkingrei @lance6716 @HuSharp

[JmPotato]

/test check-dev2

[tiprow]

@JmPotato: 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 check-dev2

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.

[HuSharp]

do we need to update this? https://github.com/pingcap/tidb/pull/49599/files#diff-21d8b7d7ec3350e90ca3e1480c0771480c746d910b4b563d86f68d374bd3bd66L1417-L1432

cc @lance6716

[JmPotato]

do we need to update this? #49599 (files)

cc @lance6716

I believe we don't need to do so because the old retry logic has been added and the original disk calculating logic has been moved to checkDiskAvail below.

[ti-chi-bot]

@HuSharp: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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.

[JmPotato]

/cc @YuJuncen

PTAL, needs a BR approver, thx.

[lance6716]

need to cherry-pick to v7.6 to avoid lightning regression

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-09 10:36:28.999249987 +0000 UTC m=+353178.583503660: ☑️ agreed by lance6716.
• 2024-01-10 01:57:44.938188826 +0000 UTC m=+408454.522442514: ☑️ agreed by CabinfeverB.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CabinfeverB, HuSharp, lance6716, YuJuncen

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 [YuJuncen,lance6716]
• br/OWNERS [YuJuncen]
• br/pkg/lightning/OWNERS [lance6716]

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]

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