win: high-resolution event-loop timer via waitable timer + IOCP - #34834

`uv__hrtimer_init` creates two kernel HANDLEs (`lfields->hrtimer` and `lfields->hrtimer_pkt`) before the remaining fallible steps in `uv_loop_init` (timer_heap malloc, `uv_mutex_init(&loop->wq_mutex)`, `uv_async_init`, `uv__loops_add`), whose `fail_*` unwind ladder `uv__free(lfields)` without closing either handle — `uv__loop_close` is not called when init fails. Practically these paths are OOM-only so it won't matter in production, but the trivial fix is to move the `uv__hrtimer_init(loop, lfie

`expect(stderr).toBe("")` will flake under ASAN/debug builds, which emit benign warnings to stderr — REVIEW.md explicitly forbids asserting stderr is exactly empty. Filter the known-benign lines first (see the `filteredStderr` pattern used a few lines up in this same file) or fold stderr into a combined `{ stdout, stderr, exitCode }` assertion.