Transaction order regression caused by 5197

[shiveshr]

Problem description
With #5197 we regressed the transaction ordering if the number of transactions in committing state are more than the limit (100) as we do not honor the order among them and end up picking 100 of them and then applying order on the chosen list.
the list should be chosen in order itself

Problem location
PersistentStreamBase

Suggestions for an improvement
Fix the bug