[3.3] Retry connect to provider server by catching ClosedChannelException

[zrlw]

What is the purpose of the change?

try to fix #15191
@AlbumenJ

... catch such exception and retry automatically. In the future, maybe 3.4, we can remove all the support of netty3 anymore. It is important to prevent importing surprising changes in minor release.

Checklist

• Make sure there is a GitHub_issue field for the change.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test to verify your logic correction. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Make sure gitHub actions can pass. Why the workflow is failing and how to fix it?

[codecov-commenter]

Codecov Report

❌ Patch coverage is 38.09524% with 26 lines in your changes missing coverage. Please review.
✅ Project coverage is 60.77%. Comparing base (91b005e) to head (b9a14d5).
⚠️ Report is 198 commits behind head on 3.3.

Files with missing lines	Patch %	Lines
...he/dubbo/remoting/transport/netty/NettyClient.java	38.09%	21 Missing and 5 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##                3.3   #15209      +/-   ##
============================================
+ Coverage     60.76%   60.77%   +0.01%     
- Complexity    10886    10892       +6     
============================================
  Files          1885     1885              
  Lines         86071    86082      +11     
  Branches      12892    12894       +2     
============================================
+ Hits          52298    52316      +18     
+ Misses        28326    28314      -12     
- Partials       5447     5452       +5     

Flag	Coverage Δ
integration-tests	33.14% <0.00%> (+0.05%)	⬆️
samples-tests	29.08% <0.00%> (-0.11%)	⬇️
unit-tests	58.93% <38.09%> (+0.03%)	⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[AlbumenJ]

we should limit the maximum times here

[zrlw]

@AlbumenJ
connectTimeout will be recalculated at here.