node:perf_hooks: support two-argument eventLoopUtilization diffs

[andrewtdiz]

Summary

Node performance.eventLoopUtilization(utilization1, utilization2) computes the delta between two prior readings. Perry's runtime helper and dispatch path only accept/pass the first argument, so the two-argument form is treated like the one-argument current - utilization1 form.

Node 25.9.0 behavior

const { performance } = require("node:perf_hooks");

const a = performance.eventLoopUtilization();
setTimeout(() => {
  const b = performance.eventLoopUtilization();
  const twoArg = performance.eventLoopUtilization(b, a);
  const oneArg = performance.eventLoopUtilization(b);
  console.log(twoArg); // roughly b - a
  console.log(oneArg); // roughly current - b, a different/smaller interval
}, 50);

Local Node v25.9.0 after the delay produced a two-argument result with about 51ms idle / 0.46ms active, while the one-argument eventLoopUtilization(b) result represented only the tiny interval after b was captured.

Perry source evidence

• crates/perry-runtime/src/perf_hooks.rs::js_perf_event_loop_utilization(prev: f64) has a single prev parameter and only computes cumulative values or current - prev.
• Dynamic dispatch in crates/perry-runtime/src/object/native_module_dispatch.rs calls js_perf_event_loop_utilization(arg(0)) and drops arg(1).
• Static lowering in crates/perry-codegen/src/lower_call/native/perf_hooks.rs also lowers only argument 0 for eventLoopUtilization.

Expected

performance.eventLoopUtilization(utilization1, utilization2) should subtract utilization2 from utilization1, matching Node. The existing zero-arg cumulative form and one-arg current - previous form should keep working.

Duplicate checks

• eventLoopUtilization two argument
• perf_hooks eventLoopUtilization util1 util2

I did not find an existing issue for the two-argument eventLoopUtilization() overload.

[andrewtdiz]

I am taking this in a focused node:perf_hooks timing and validation PR cut with #3012, #3013, #3010, #3008, and #3088. Intended scope: make performance.now() relative to a process-start timeOrigin, support two-argument eventLoopUtilization() diffs, and align the related User Timing / observer validation behavior. Non-goals: timerify() function entries and markResourceTiming() resource entries, which fit a separate observable-entry cut.

[andrewtdiz]

Opened PR #3508 to close this: #3508

Verification on the rebased branch:

• Node 24 parity: ./run_parity_tests.sh --suite node-suite --module perf_hooks passed 78/78.
• cargo check -p perry-runtime -p perry-codegen -p perry-hir -p perry-api-manifest -p perry passed.
• cargo fmt --all -- --check, ./scripts/check_file_size.sh, jq empty test-parity/known_failures.json, and git diff HEAD~1..HEAD --check passed.