[Bug] 删除边时出现 Edges size has reached tx capacity 10000

### Bug Type (问题类型)

rest-api (结果不合预期)

### Before submit

- [X] 我已经确认现有的 [Issues](https://github.com/hugegraph/hugegraph/issues) 与 [FAQ](https://hugegraph.github.io/hugegraph-doc/guides/faq.html) 中没有相同 / 重复问题

### Environment (环境信息)

- Server Version: v0.11.x
- Backend: RocksDB x nodes, HDD or SSD
- OS: xx CPUs, xx G RAM, Centos 7.x
- Data Size: xx vertices, xx edges

### Expected & Actual behavior (期望与实际表现)

数据里面，有超过500W的点和1000W以上的边，数据导入时，因为源数据有问题，所以想删除已经导入的数据，重新导入，在执行了g.E().hasLabel('XXX').drop()以后出现错误 Edges size has reached tx capacity 10000的提示，删除点的时候也出现过这种提示。

### Vertex/Edge example (问题点 / 边数据举例)

_No response_

### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

_No response_

Start by reproducing the g.E().hasLabel('XXX').drop() operation on HugeGraph v0.11.x with more than 10,000 matching edges or vertices, using the REST API and the reported backend setup where possible. Trace how deletion operations enforce transaction capacity and identify the relevant transaction or bulk-deletion entry point; done means large deletions no longer fail solely at the 10,000-item limit and regression coverage verifies the behavior.

Written by the indexing model from the issue text.