"Re-run test in a folder whose name contains unusual chars" test is flaky

[alexsch01]

Test

Re-run test in a folder whose name contains unusual chars

Platform

macOS ARM64

Console output

/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 /(?:assert|break|break on start|debugCommand|exception|other|promiseRejection|step) in/i

Build links

• https://github.com/nodejs/node/actions/runs/21828756273/job/62980757504
• https://github.com/nodejs/node/actions/runs/21785139333/job/62855280668
• https://github.com/nodejs/node/actions/runs/21772762644/job/62823422649
• https://github.com/nodejs/node/actions/runs/21760776466/job/62783508438
• https://github.com/nodejs/node/actions/runs/21753799897/job/62758397337

Additional information

I saw https://github.com/nodejs/node/pull/61708/commits sporadically failing in CI for "Test macOS / test-macOS (pull_request)"

[inoway46]

Opened #61773 as a targeted mitigation for restart-related debugger test flakiness.
The hypothesis is a timing race around restart/reconnect output ordering (possibly involving test/common/debugger.js synchronization), but root cause is not conclusively proven yet.
This PR narrows synchronization in the affected tests while preserving their assertions.

[inoway46]

Quick status update:

From recent macOS unusual-path failures, test-debugger-restart-message.js appears to be the most frequent failure, while other debugger test timeouts seem more sporadic.

Examples:

• https://github.com/nodejs/node/actions/runs/22268117105
• https://github.com/nodejs/node/actions/runs/22267555605
• https://github.com/nodejs/node/actions/runs/22267166673

PR #61773 is intentionally scoped to the restart synchronization path and keeps the change set small (test-debugger-restart-message.js + test-debugger-run-after-quit-restart.js).

I did not include other restart-adjacent tests (for example, test-debugger-exceptions.js) in the same PR to avoid broadening review scope with different assertion paths.

If flakes continue after #61773 lands, I can follow up with additional targeted PRs for the other affected tests.