[fix][broker] Fix occur confusing error log when reader readEntry

[TakaHiR07]

Main Issue: https://github.com/apache/pulsar/issues/23022

Motivation

As shown in the issue. Fix occur confusing error log when use reader to read entry.

Modifications

In the case that read entry failed because cursor is NonDurableCursor and is closed , there is no need to trigger more read operations since the next read operation would directly skip and finish. Just wait for a new NonDurableCursor open and read again.

This is the simplest way I guess to fix the problem. This fix only affect the nonDurableCursor, which would not bring extra issue of durableCursor

Verifying this change

• [x] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• [ ] Dependencies (add or upgrade a dependency)
• [ ] The public API
• [ ] The schema
• [ ] The default values of configurations
• [ ] The threading model
• [ ] The binary protocol
• [ ] The REST endpoints
• [ ] The admin CLI options
• [ ] The metrics
• [ ] Anything that affects deployment

Documentation

• [ ] doc
• [ ] doc-required
• [x] doc-not-needed
• [ ] doc-complete