An incorrect early return caused processing of due timers to stop
prematurely.

Fixes: nodejs#50382

mocked setInterval used the wrong increment when scheduling the new
timer.

Fixes: nodejs#50382

Removal of mocket timers from the priority queue was broken. It used the
timerId instead of the position in the queue as index. This lead to
removal of incorrect timers from the queue causing timers not to be
scheduled at all.

Also, aborts caused removal from the queue even when the timer was
already triggered, and thus no longer present in the queue.

Fixes: nodejs#50365

Co-authored-by: Raz Luvaton <[email protected]>