Fix context range precision gap

[ddelemeny]

When looking backwards on a searchAfter request, createContextTimerange creates a range which does not contain the searchAfter target timestamp row.timeEpochNs because of truncated precision.

This PR does the following :

• offset the higher bound by 1 Ms to make sure that the target timestamp is within the bounds after truncation.
• add a test to check that scenario