Pulsar 2.5.0 regression: Reader.hasMessageAvailable returns false when startMessageId is the message id of the last message id in startMessageIdInclusive mode

[lhotari]

Description
Reader.hasMessageAvailable returns false when startMessageId is the message id of the last message id in startMessageIdInclusive mode.
If the message id is any other id than the id of the last message, there is no issues.
This problem occurs with Pulsar 2.5.0. The test case passes with Pulsar 2.4.2.

To Reproduce
Steps to reproduce the behavior:

git clone -b has-message-available-2.5.0 https://github.com/lhotari/pulsar-bug-repro
cd pulsar-bug-repro
./gradlew test

The repository that includes the test case is https://github.com/lhotari/pulsar-bug-repro .

To test with Pulsar 2.4.2 (test passes)

git checkout has-message-available-2.4.2
./gradlew cleanTest test

Expected behavior
When using the Reader API and specifying the message id of the message id of the last message that exists in the topic with startMessageIdInclusive mode, then Reader.hasMessageAvailable should return true.

[lhotari]

When running the test case multiple times, it sometimes passes even on Pulsar 2.5.0, so there is a flaky nature in this bug. This issue might be related to #6224.