test: avoid flaky restart sync in debugger exceptions test

[inoway46]

In test/parallel/test-debugger-exceptions.js, using stepCommand('r') can intermittently time out while waiting for BREAK_MESSAGE. This PR preserves the test intent, but changes the reconnect sync point for r to wait for ok before waitForInitialBreak().

Same approach as #62807

CI logs

• https://github.com/nodejs/node/actions/runs/22025863299 (line:30)
• https://github.com/nodejs/node/actions/runs/22532700362 (line:41)
• https://github.com/nodejs/node/actions/runs/22632786580 (line:49)

Testing

UNUSUAL="$HOME/dir with \$unusual\"chars?'åß∂ƒ©∆¬…\`"
mkdir -p "$UNUSUAL"
ln -sfn "$PWD" "$UNUSUAL/node"
cd "$UNUSUAL/node"

• ./tools/test.py -p actions parallel/test-debugger-exceptions
• ./tools/test.py -p actions -j1 --repeat 40 parallel/test-debugger-exceptions
• ./tools/test.py -p actions parallel/test-debugger-restart-message parallel/test-debugger-run-after-quit-restart
• CI passes on macOS

Refs: #61762

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.68%. Comparing base (58a8e1d) to head (1b3d3fe).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #62055      +/-   ##
==========================================
- Coverage   89.69%   89.68%   -0.01%     
==========================================
  Files         706      706              
  Lines      218222   218222              
  Branches    41768    41771       +3     
==========================================
- Hits       195731   195711      -20     
- Misses      14411    14418       +7     
- Partials     8080     8093      +13     

see 27 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/72190/

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[inoway46]

Since the Windows flakiness seems better now, could you please rerun CI for this PR?

[nodejs-github-bot]

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

[inoway46]

https://ci.nodejs.org/job/node-test-commit-windows-fanned/76495/console
It looks like this failure happened around git-rebase and the temp-ref handoff, possibly due to a race while the downstream job was trying to read the temp ref. Could someone please rerun CI for this PR?

I'm not sure this will help, but rebasing this branch onto the latest upstream/main may reduce the chance of this. If the next rerun fails again, I'll rebase onto upstream/main and force-push.

[nodejs-github-bot]

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