[Bug] 数据同步问题

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

current version

### Describe the bug and provide the minimal reproduce step

多副本情况下， data region leader wal 数据有积压， 切换到 follow 以后,客户端 接着写入 ，由于 LogDispatcher 维护的 index 是不同的， 导致数据 不是严格有序的。 如果都是 insert ， 没有问题， 但是如果 有 delete 操作， 会出现数据 丢失问题。

### What did you expect to see?

-

### What did you see instead?

-

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start with the LogDispatcher state described in the issue and trace how its index changes when a data region switches from leader to follower. Reproduce the multi-replica scenario with pending WAL data and subsequent client writes, including delete operations; done means writes remain strictly ordered and deletes no longer cause data loss.

Written by the indexing model from the issue text.