debugger: await initialization after run and restart

[trivikr]

Fix a debugger CLI synchronization race after run and restart.

Previously, these commands resolved once the inspector websocket connection
was established and ok was printed. The debugger initialization that enables
domains, restores breakpoints, and calls Runtime.runIfWaitingForDebugger()
was started from the ready event but not awaited.

That allowed the REPL prompt to be displayed before the restarted debuggee had
actually been released from --inspect-brk and reported the initial break. In
slow CI runs, this could make parallel/test-debugger-run-after-quit-restart
time out while waiting for the initial break message.

This changes run and restart to await the same post-connect initialization
path before resolving.

Observed in:

• https://github.com/nodejs/node/actions/runs/26499357103/job/78035468302
• https://github.com/nodejs/node/actions/runs/26555566216/job/78236783282
• https://github.com/nodejs/node/actions/runs/26561872119/job/78246617313

Error Log

Path: parallel/test-debugger-run-after-quit-restartError: --- stderr ---/Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/common/debugger.js:92 const timeoutErr = new Error(`Timeout (${TIMEOUT}) while waiting for ${pattern}`); ^Error: Timeout (15000) while waiting for /break (?:on start )?in/i at /Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/common/debugger.js:92:28 at new Promise (<anonymous>) at Object.waitFor (/Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/common/debugger.js:67:14) at Object.waitForInitialBreak (/Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/common/debugger.js:116:18) at /Users/runner/work/node/node/dir%20with $unusual"chars?'åß∂ƒ©∆¬…`/test/parallel/test-debugger-run-after-quit-restart.js:46:21 at process.processTicksAndRejections (node:internal/process/task_queues:104:5) { output: '< Debugger listening on ws://127.0.0.1:62843/a2167dba-9191-46bd-8b81-4245173caea4\n' + '< For help, see: [https://nodejs.org/learn/getting-started/debugging\n](https://nodejs.org/learn/getting-started/debugging/n)' + '< \n' + '\n' + 'debug> connecting to 127.0.0.1:62843 ...\n' + '\n' + '< Debugger attached.\n' + '< \n' + '\n' + 'debug> \n' + ' ok\n' + 'debug> '}

Refs: #61762

---

Assisted-by: openai:gpt-5.5

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.32%. Comparing base (4639dcb) to head (30e43c1).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #63607 +/- ##
==========================================
+ Coverage 90.29% 90.32% +0.02% 
==========================================
Files 730 730 Lines 234695 234709 +14 Branches 43956 43963 +7 ==========================================
+ Hits 211927 211993 +66 + Misses 14494 14434 -60 - Partials 8274 8282 +8 

Files with missing lines	Coverage Δ
lib/internal/debugger/inspect_repl.js	91.78% <100.00%> (+0.01%)	⬆️

... and 53 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/74146/

[nodejs-github-bot]

Landed in c2f2013

[trivikr]

This change did not help, as test-debugger-run-after-quit-restart continues to fail as reported in #64005