[Bug] [Broker] Entry digest does not match

### Search before asking

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

### Version

2.9

### Minimal reproduce step

We use **transactinal feature** and start some tasks.

### What did you expect to see?

.

### What did you see instead?

One entry can't be read out because entry digest does not match, we have meet this problem serveral times, but the frequency of occurrency is pretty low.

The replication factor is `3 3 2`, so there are 3 copy of this entry. Further, i find that all of these three copy are same, which exclude the possibility of disk error. There must be something wrong with the code.

### Anything else?

_No response_

### Are you willing to submit a PR?

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

Start with the reported transactional-feature reproduction in the broker and the entry-digest mismatch symptom. The issue names no source file, test, or entry point, so trace the broker's replicated-entry read and digest handling first. Done means identifying and correcting the cause so replicated copies can be read without a digest mismatch.

Written by the indexing model from the issue text.