optimize: modify judgment conditions when use retry and err = nil

[li-jin-gou]

What type of PR is this?

optimize

Check the PR title.

• This PR title match the format: <type>(optional scope): <description>.
• The description of this PR title is user-oriented and clear enough for others to understand.
• Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo.

(Optional) Translate the PR title into Chinese.

• 修改使用 retry 并且 err = nil 时的判断条件

zh(optional):

(Optional) Which issue(s) this PR fixes:

(Optional) The PR that updates user documentation:

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (2bd70be) 75.87% compared to head (e256bde) 75.87%.

❗ Current head e256bde differs from pull request most recent head 8688557. Consider uploading reports for the commit 8688557 to get more accurate results

Additional details and impacted files

@@           Coverage Diff            @@
##           develop     #860   +/-   ##
========================================
  Coverage    75.87%   75.87%           
========================================
  Files           97       97           
  Lines         9512     9512           
========================================
  Hits          7217     7217           
  Misses        1846     1846           
  Partials       449      449           

Impacted Files	Coverage Δ
pkg/protocol/http1/client.go	59.59% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[li-jin-gou]

PATL @welkeyever @FGYFFFF @wzekin

[welkeyever]

LGTM, but there is a small risk: this change may cause the business that did not enter the custom retry logic to enter the retry logic when err == nil.