[Feature] UT Phase Takes Too Long During CI Execution, Needs Analysis and Optimization

### Pre-check

- [x] I am sure that all the content I provide is in English.

### Search before asking

- [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar feature requirement.

### Apache Dubbo Component

Java SDK (apache/dubbo)

### Descriptions

In the current Dubbo CI process, the unit test (UT) phase takes a relatively long time, which affects overall efficiency during development and PR submissions. We need to:

- [ ] Which modules are the most time-consuming during UT?

- [ ] Are there any redundant tests or inefficient test cases?

- [ ] Is the lack of parallelism slowing down the test execution?

Any suggestions or contributions are welcome!

### Related issues

_No response_

### Are you willing to submit a pull request to fix on your own?

- [ ] Yes I am willing to submit a pull request on my own!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)