🧪 test(serialize): widen the node differential timeout

[gaborbernat]

The Windows 3.10 cell of #704 went red on test_folding_preserves_behavior[literals]. That case is the first in tests/serialize/js/test_fold.py to launch node, and subprocess.run raised TimeoutExpired at its 60s bound. The job's slowest-durations table puts the next case at 14.92s for its two launches and nothing else in the file above a second, which points at a one-time cost to start a cold node.exe. Which case pays that cost depends on collection order, so the failure moves around.

The bound exists to stop a snippet that never returns from wedging the run, so it goes to 300s, past a slow process start and still short enough to catch a hang. tests/serialize/js/test_mangle.py runs the same helper against the mangling differential and carried the same 60s bound, so both move together.

The tests/conformance suites that shell out to node keep their 120s bounds. That job runs only on ubuntu-24.04, where this cold-start cost has not shown up.

[codspeed-hq]

Merging this PR will not alter performance

✅ 107 untouched benchmarks
⏩ 29 skipped benchmarks¹

---

_{Comparing gaborbernat:fix/node-differential-timeout (8093538) with main (401a2dc)}

Footnotes

1. 29 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩