What is the current behavior?

The current setInterval function uses a problematic timing calculation that causes drift and incorrect behavior when callbacks take time to execute.
Root Cause: The current implementation tries to align intervals to wall-clock time using:

const startOffset = milliseconds > 0 ? Date.now() % milliseconds : 0;
function nextCallMs() {
    return milliseconds > 0 ? milliseconds - ((Date.now() - startOffset) % milliseconds) : milliseconds;
}

This causes:
Extra callbacks in test_setInterval_callbackNotDelayedByBusyWork because the timing calculation doesn't account for callback execution time properly
Missed callbacks in test_setInterval_callbackSkippedByBusyWork because the busy work throws off the timing alignment

What is the new behavior?

The implementation follows the same pattern as the native C++ implementation in the android runtime, which updates the start time after each execution to prevent drift.