多租户问题

系统目前已经按用户、资金、订单、活动等进行服务切分，采用seata作为事务的同步。因为每个租户的订单业务数据量增长比较快，需要将订单按租户存放到不同的库里面，底层的分库考虑用mycat，按官方文档mycat也是有事务管理的，这个与seata是否冲突，能否整合。

No files, tests, or entry points are named. Start by reviewing the issue's described Seata transaction setup and Mycat's official transaction documentation, then determine whether tenant-based order database sharding can coexist with Seata. Done would require a documented compatibility or integration approach, rather than a single localized code change.

Written by the indexing model from the issue text.