fix: Clock inaccuracy in libuv is causing flaky tests.

[jdmarshall]

github.com/libuv/libuv/issues/4773

This isn't fixed until Node 24.?? so your tests will be flaky as long as you're validating on 20 and 22

[RafaelGSS]

To be honest, that's irrelevant to us. Those additional 0.999 (or extra) shouldn't affect this test suite. Have you experienced a flaky test from time-mode?

This hasn't been fixed in any of Node.js versions (there's no ready fix by libuv team).

[RafaelGSS]

I will accept this since it seems necessary to rebase #139.

[jdmarshall]

I’ve maintained CI pipelines for more than fifteen years and if there is one thing that experience has taught me time and time again, it’s how few flaky tests are required before people start ignoring legitimate problems in the build failures. “That build is always failing so I just reran it [three times]”