Fix issue in getOverlappingRedactionRanges.

The code mistakenly assumed that hasOverlapWithReadRequest
was a precise check, which isn't the case. It can return true
even if the read range does not overlap, therefore we must
always check whether we've found an overlap.

Bug: 171467335
Test: atest RedactionInfoTest
Change-Id: I3f0cc0628dd91f04490a005a6567a00153faac03
2 files changed