Remove MainTestClockImpl.onTimeAdvanced

[m-sasha]

Now that we have a rendering loop in tests, it's no longer necessary to call render every time the test clock is advanced. In fact, it is incorrect to do so. The following test succeeds on Android, but fails on the desktop:

    @Test
    fun advancingClockByLessThanFrameDoesNotRecompose() = runComposeUiTest {
        mainClock.autoAdvance = false
        var value by mutableIntStateOf(1)
        var compositionValue = 0
        setContent {
            compositionValue = value
        }
        assertEquals(1, compositionValue)
        value = 2
        mainClock.advanceTimeBy(1, ignoreFrameDuration = true)
        assertEquals(1, compositionValue)
    }

Following that, our changes to AbstractMainTestClock are no longer needed, and Upstreaming. commonization. ui-test. AbstractMainTestClock is also no longer needed.

Fixes https://youtrack.jetbrains.com/issue/CMP-5776/Upstreaming.-commonization.-ui-test.-AbstractMainTestClock

Testing

Added a new unit test.

Release Notes

Breaking Changes - Multiple Platforms

• Advancing mainClock such that it doesn't reach the next frame, will no longer cause a recomposition.