Some unit tests in the PR have failed. Could you help take a look at the reasons?

### Check Ahead

- [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.

- [ ] I am willing to try to fix this bug myself.

### Ⅰ. Issue Description

I ran the tests three times, and each time the failed unit tests were different. Here is my PR: https://github.com/apache/incubator-seata/pull/7480. I believe these failed tests are not related to my changes, because they have passed before and I cannot reproduce the failures locally.

Failed test runs:
https://github.com/apache/incubator-seata/actions/runs/16294178668

https://github.com/apache/incubator-seata/actions/runs/16293163634

https://github.com/apache/incubator-seata/actions/runs/16289254489

For example, in this run: https://github.com/apache/incubator-seata/actions/runs/16289254489, it shows that the dm driver cannot be found, but I did not modify any related code.

### Ⅱ. Describe what happened

_No response_

### Ⅲ. Describe what you expected to happen

_No response_

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

_No response_

### Ⅴ. Anything else we need to know?

_No response_

### Ⅵ. Environment

_No response_

Review PR #7480 and the three linked GitHub Actions runs, starting with their failed unit-test logs. Compare the varying failures, including the missing DM driver message, against the PR changes and CI environment. Done means the failure cause is identified and the relevant CI or test issue is fixed or clearly documented.

Written by the indexing model from the issue text.