Read remote metadata once during application runtime

[finefuture]

What is the purpose of the change?

The local cache file may be damaged for various reasons, resulting in a no provider exception, so I recommend reading the remote metadata once during the application running process.

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

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 60.77%. Comparing base (a9e4910) to head (dff48ec).

Files with missing lines	Patch %	Lines
...ubbo/registry/client/AbstractServiceDiscovery.java	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##                3.3   #15006      +/-   ##
============================================
+ Coverage     60.76%   60.77%   +0.01%     
  Complexity    10866    10866              
============================================
  Files          1882     1882              
  Lines         85983    85988       +5     
  Branches      12876    12876              
============================================
+ Hits          52246    52258      +12     
+ Misses        28289    28282       -7     
  Partials       5448     5448              

Flag	Coverage Δ
integration-tests	32.99% <83.33%> (-0.15%)	⬇️
samples-tests	29.23% <83.33%> (+<0.01%)	⬆️
unit-tests	58.91% <83.33%> (+<0.01%)	⬆️

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.