1.1 1.2 自动代理数据源失败

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

### Ⅰ. Issue Description
1.1 1.2 版本自动代理数据源失败
导致server端resourceIds 为null，后续事务回滚失败

### Ⅱ. Describe what happened


### Ⅲ. Describe what you expected to happen

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

seata:
enabled: true
application-id: ${spring.application.name}
tx-service-group: my_tx_group
registry:
type: nacos
nacos:
cluster: default
server-addr: 127.0.0.1:8848
namespace: 7eb28e8d-b2a0-466f-b48d-7528067b518f
group: SEATA_REG_GROUP
service:
vgroup-mapping:
my_tx_group: default
config:
type: nacos
nacos:
namespace: 7eb28e8d-b2a0-466f-b48d-7528067b518f
serverAddr: 127.0.0.1:8848
group: SEATA_CONFIG_GROUP

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

### Ⅵ. Environment:

- JDK version : 1.8
- OS : window10

Start by reproducing the failure with the Seata, Nacos, and Spring configuration shown in the issue on JDK 1.8 and Windows 10. Investigate why the server-side resourceIds is null during automatic datasource proxying; done means the resourceIds is populated and subsequent transaction rollback succeeds.

Written by the indexing model from the issue text.