test: fix flaky debugger test

[islandryu]

For some reason, I’ve lost Jenkins permissions and can’t post the detailed URL, but I’m modifying the contents of this CI:
https://ci.nodejs.org/job/node-test-commit/79774/

I encountered this on my Windows machine when running this command.

 python3 tools/test.py --repeat=10000 parallel/test-debugger-break

node/test/parallel/test-debugger-break.js

Lines 37 to 44 in b197355

	await cli.stepCommand('next');
	assert.ok(
	cli.output.includes(`step in ${script}:3`),
	'pauses in next line of the script');
	assert.match(
	cli.output,
	/> 3 name = 'Robin';/,
	'marks the 3nd line');

The cause was the output of the cont command.
Normally, it looks like this

< Hello Robin
< 
break in test/fixtures/debugger/break.js:10
  8 }
  9 sayHello();
>10 debugger;
 11 setTimeout(sayHello, 10);
 12 
debug> 

However, on rare occasions, the order of the debugger output and standard output is reversed like this:

break in test/fixtures/debugger/break.js:10
  8 }
  9 sayHello();
>10 debugger;
 11 setTimeout(sayHello, 10);
 12 
debug> 
< Hello Robin
< 
debug> 

So I modified it to wait for the corresponding response before proceeding to the next command.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.24%. Comparing base (a822a1c) to head (9a420b5).
Report is 39 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58324      +/-   ##
==========================================
+ Coverage   90.17%   90.24%   +0.07%     
==========================================
  Files         631      633       +2     
  Lines      186652   186818     +166     
  Branches    36660    36672      +12     
==========================================
+ Hits       168312   168594     +282     
+ Misses      11121    11029      -92     
+ Partials     7219     7195      -24     

see 45 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/66799/

[nodejs-github-bot]

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