[Bug] read entry failed cause `No such ledger exists on Bookies` with Orphan non-durable cursor

### Search before asking

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

### Read release policy

- [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

### Version

2.10.4

### Minimal reproduce step

tmp

### What did you expect to see?

tmp

### What did you see instead?

1. I found that there are intermittent read request failures on 3 bookies in the cluster.

2. It can be seen from the logs, These read requests come from trying to read a non-existent ledger, and the ensemble for this ledger consists of these three bookies.
3. Related log as follows:
4. loop 3 in broker side.
(This topic has no message in for a long time and no subscription.)

### Anything else?

_No response_

### Are you willing to submit a PR?

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

Start by reproducing the intermittent read failures on Pulsar 2.10.4, focusing on broker requests from an orphan non-durable cursor and the related bookies. Compare the logs for reads of nonexistent ledgers and determine what would prevent the broker-side loop; done means those reads no longer fail intermittently or loop.

Written by the indexing model from the issue text.