[3.3] Replace ConcurrentHashMap#computeIfAbsent for performance improvement and prevention of deadlock

[zrlw]

What is the purpose of the change?

Fix the codes that still use ConcurrentHashMap#computeIfAbsent which might have performance issue and deadlock risk,
see details at

1. ConcurrentHashMapUtils无法解决jdk8的循环bug
2. dubbo.metrics publishEvent blocked on ConcurrentHashMap.computeIfAbsent

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

Project coverage is 60.96%. Comparing base (4f5ca88) to head (ade6e29).

Files with missing lines	Patch %	Lines
.../registry/zookeeper/ZookeeperServiceDiscovery.java	83.33%	2 Missing ⚠️
...apache/dubbo/common/serialization/ClassHolder.java	50.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##                3.3   #15456      +/-   ##
============================================
+ Coverage     60.94%   60.96%   +0.01%     
+ Complexity    11454    11453       -1     
============================================
  Files          1888     1888              
  Lines         86368    86377       +9     
  Branches      12958    12958              
============================================
+ Hits          52640    52660      +20     
+ Misses        28295    28282      -13     
- Partials       5433     5435       +2     

Flag	Coverage Δ
integration-tests-java17	33.11% <82.67%> (+<0.01%)	⬆️
integration-tests-java8	33.14% <82.67%> (+<0.01%)	⬆️
samples-tests-java17	31.43% <79.52%> (-0.01%)	⬇️
samples-tests-java8	29.38% <75.59%> (+0.02%)	⬆️
unit-tests	58.88% <94.48%> (+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.

🚀 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.

[zrlw]

@oxsean PTAL

[oxsean]

LGTM.