chore: Use ReentrantLock for inti ReferenceConfig.

[He-Pin]

What is the purpose of the change

Avoid pinning the carrier thread.

    org.apache.dubbo.registry.client.migration.MigrationRuleHandler.doMigrate(MigrationRuleHandler.java:60) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:268) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:268) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) <== monitors:1
    org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) <== monitors:1

Brief changelog

Use ReentrantLock.

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[AlbumenJ]

Please fix the code style

[He-Pin]

@AlbumenJ Thanks, I have updated

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[He-Pin]

thanks @AlbumenJ