[2.x] Fix wrong behavior of hasMessageAvailable after seeking by timestamp

[RobertIndie]

Motivation

Cherry-pick #333 to 2.x branch.

The reader's HasMessageAvailableAsync may return true after a timestamp-based seek, even if there are no available messages in the topic.

Modifications

Add a boolean flag HasSoughtByTimestamp to represent whether the last seek call accepts a timestamp. If it's true, don't take startMessageId into comparison with lastMessageIdInBroker, just compare the mark-delete position and last position in the GetLastMessageId response.

[RobertIndie]

The CI is failed related to this issue: #343. Could you help try rerun it? @Lanayx

[Lanayx]

@RobertIndie Before we do the backport can you please comment on the two issues

1. This ticket Unexpected reading behaviour after seeking by time and using HasMessageAvailableAsync #340
2. I've recently realized that hasSoughtByTimestamp never returns back to false, once set to true it stays there forever. Shouldn't it be reset after subscription is reestablished?

[Lanayx]

The CI is failed related to this issue: #343. Could you help try rerun it? @Lanayx

Done

[RobertIndie]

@RobertIndie Before we do the backport can you please comment on the two issues

1. This ticket Unexpected reading behaviour after seeking by time and using HasMessageAvailableAsync #340
2. I've recently realized that hasSoughtByTimestamp never returns back to false, once set to true it stays there forever. Shouldn't it be reset after subscription is reestablished?

Thanks! I pushed a PR to address both these issues: #344.

[Lanayx]

Thanks for addressing that PR. Do your want to includes those commits in this PR?

As I side note - it looks like we don't need to support 2.x any longer, based on nuget numbers nobody uses latest 2.x packages.

[RobertIndie]

Thanks for addressing that PR. Do your want to includes those commits in this PR?

I include that commit to this PR as well now.

As I side note - it looks like we don't need to support 2.x any longer, based on nuget numbers nobody uses latest 2.x packages.

Some of our users are still relying on version 2.x.

[Lanayx]

Some of our users are still relying on version 2.x.

Right, but nobody uses versions above 2.16.0