test: increase debugger waitFor timeout on macOS and Windows

[mcollina]

Summary

• Increase the macOS/Windows debugger test timeout from 15s to 30s

The test-debugger-restart-message test is flaky on macOS CI. The Debugger.on('paused') handler in the inspect REPL prints the "break in" message only after an async Debugger.getScriptSource CDP round-trip to V8 completes. On loaded macOS CI machines, this round-trip can exceed the 15s timeout.

The timeout has already been bumped twice (5s→10s in #56970, 10s→15s for macOS in #60367). platformTimeout() applies no multiplier for macOS, so the raw ms value is the actual timeout. Doubling to 30s provides adequate headroom.

Test plan

• test-debugger-restart-message passes locally
• CI passes on macOS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.77%. Comparing base (ae2ffce) to head (bc6562f).
⚠️ Report is 293 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #61902 +/- ##
==========================================
+ Coverage 89.75% 89.77% +0.01% 
==========================================
Files 674 674 Lines 204416 204886 +470 Branches 39285 39377 +92 ==========================================
+ Hits 183472 183929 +457 
Misses 13227 13227 - Partials 7717 7730 +13 

see 78 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/71383/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/71385/

[lpinca]

I don't think increasing the timeout solves the underlying issue. IIRC we already did in the past. #61773 might be a proper fix. I haven't approved it yet because I haven't thoroughly reviewed it.

cc: @inoway46

[inoway46]

Thanks for the mention.

If helpful, I'll run additional local verification on my PR side (A/B against main under unusual-path conditions) and share the results to confirm whether it addresses the issue.

CI for my PR is now running as well, so that may help confirm whether the flake still reproduces.