Test cases are flaking in the FakeOppiaClockTest

Describe the bug A clear and concise description of what the bug is. The test cases testGetCurrentCalendar_wallClockMode_returnsCalendarWithCurrentTimeMillis() and testGetCurrentTimeMs_wallClockMode_returnsCurrentTimeMillis are flaky.

Failure error -

expected to be in range: (1616173019436..1616173019440)
but was                : 1616173019440

	at org.oppia.android.testing.time.FakeOppiaClockTest.isWithin(FakeOppiaClockTest.kt:262)
	at org.oppia.android.testing.time.FakeOppiaClockTest.testGetCurrentCalendar_wallClockMode_returnsCalendarWithCurrentTimeMillis(FakeOppiaClockTest.kt:194)

Expected behavior The test cases should always pass.

Screenshots If applicable, add screenshots or videos to help explain your problem. When run 100 times, the test case failed 1 time -

Sometimes failing on CI checks -

[prayutsu]

@Karanjot-singh If you carefully take a look at the assertion of the test -

assertThat(reportedTimeMs).isWithin((currentTimeMs - 2)..(currentTimeMs + 2))

you can see that we check that if reportedTime lies in the range [ currentTime-2, currentTime+2 ] or not, which is a very small range, although currentTime and reportedTime are initialized one after another but the difference between their actual values can vary more than that. So, the current buffer range for the reportedTime is 4 ms, but we want to increase it to 100 ms. Does that make sense?

[anandwana001]

@prayutsu It will be helpful if you add the failure result.