Using sharding-proxy, seata cannot roll back the transaction normally when XA transaction is not started.

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

### Ⅰ. Issue Description
使用sharding-proxy在不开启XA事务时seata无法正常回滚事务

### Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

```
Just paste your stack trace here!
```

### Ⅲ. Describe what you expected to happen
使用sharding-proxy不开启XA事务seata可以正常回滚事务

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

1. xxx
2. xxx
3. xxx

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

### Ⅵ. Environment:

- JDK version :
- OS :
- Others:

Start by constructing a minimal Seata reproduction using sharding-proxy with XA transactions disabled; the issue provides no concrete steps, stack trace, environment, files, or tests. Trace the transaction path to determine why rollback fails, then verify that the same scenario rolls back normally and add a precise regression test or reproduction.

Written by the indexing model from the issue text.