fix(test): Improve reliability of deno test's op sanitizer with timers

[andreubotella]

Although not easy to replicate in the wild, the deno test op sanitizer can fail when there are intervals that started before a test runs, since the op sanitizer can end up running in the time between the timer op for an interval's run resolves and the op for the next run starts.

This change fixes that by adding a new macrotask callback that will run after the timer macrotask queue has drained. This ensures that there is a timer op if there are any timers which are unresolved by the time the op sanitizer runs.

[andreubotella]

This is needed to fix some of the CI failures in #12862

[andreubotella]

@bartlomieju @caspervonb PTAL

[caspervonb]

LGTM!

[bartlomieju]

LGTM!

I verified that provided test case fails on main. Good fix @andreubotella

[kt3k]

This change seems breaking some test cases in deno_std (e.g. node/_util/_util_callbackify_test.ts, node/crypto_test.ts, node/http_test.ts) ref: denoland/std#1651

[kt3k]

Reproduced the issue with a smaller example. It seems related to nextTick:

import { nextTick } from "https://deno.land/std@0.116.0/node/_next_tick.ts";
Deno.test("test 1", async () => {
  await new Promise<void>((resolve) => nextTick(resolve));
});
Deno.test("test 2", async () => {
  await new Promise<void>((resolve) => nextTick(resolve));
});

The above example is stuck at the end of test 2