Check the md5 of the metadata cache file

[finefuture]

What is the purpose of the change?

The local cache file may be damaged for various reasons, resulting in a no provider exception, check the consistency of md5 can avoid this problem.

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 82.35294% with 3 lines in your changes missing coverage. Please review.

Project coverage is 60.74%. Comparing base (2582d78) to head (88092cf).

Files with missing lines	Patch %	Lines
...gistry/client/metadata/store/MetaCacheManager.java	50.00%	1 Missing and 1 partial ⚠️
...rg/apache/dubbo/metadata/AbstractCacheManager.java	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##                3.3   #15006   +/-   ##
=========================================
  Coverage     60.74%   60.74%           
+ Complexity    10873    10868    -5     
=========================================
  Files          1882     1882           
  Lines         86007    86015    +8     
  Branches      12886    12886           
=========================================
+ Hits          52244    52254   +10     
- Misses        28311    28315    +4     
+ Partials       5452     5446    -6     

Flag	Coverage Δ
integration-tests	32.99% <58.82%> (-0.07%)	⬇️
samples-tests	29.22% <58.82%> (+<0.01%)	⬆️
unit-tests	58.90% <82.35%> (-0.02%)	⬇️

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.