Currently, exhaustiveFind in the transaction API only allows finds with the singleBatch option set. To make the find useful for reads that can return more than one batch of data, we should update that method to detect when there is more than one batch (by checking the original response) and iterating the find's cursor until it's exhausted before returning to the caller.