ATR entry missing when forceATREntryToBeExpired() is called

Tests: ExtBinarySupportCleanupTest.binaryInsertInLostAbortedTransactionCanBeCleanedUpViaLostProcess
ExtBinarySupportCleanupTest.binaryInsertInLostCommittedTransactionCanBeCleanedUpDirectly
ExtBinarySupportCleanupTest.binaryInsertInLostCommittedTransactionCanBeCleanedUpViaLostProcess
ExtBinarySupportCleanupTest.binaryInsertInLostPendingTransactionCanBeCleanedUpViaLostProcess
ExtBinarySupportCleanupTest.binaryReplaceInLostAbortedTransactionCanBeCleanedUpViaLostProcess

Taking example of binaryReplaceInLostAbortedTransactionCanBeCleanedUpViaLostProcess - 
The tests are failing with error:

Did not find any entries for transaction 1166a53c-327d-436e-a0a5-e2818f83bd67 on ATR collection default._default._default - remember that ATR collection is by default on default collection of bucket of first mutated doc 

as there is no entry present when we are trying to fetch ATR entry list here.

Attaching perf and driver logs.

This behaviour is seen with cleanup being disabled explicitly in on-prem cluster (can't probably be cleanup related issue)