test: move test-debugger-address to parallel

[Trott]

The test uses --inspect=0 so it uses an OS-selected port rather than
the default port. This means it can be run in the parallel directory.

[nodejs-github-bot]

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

[Trott]

Landed in c2e6822

[mvillaizan]

When using --inspect=0, is it possible to recover the port in use?

If running a fork, how would that work?

var worker = cp.fork('./my-script', {execArgv: ["--inspect=0"]});

Under what mechanism can the port used by the inspector be recovered?

[Trott]

When using --inspect=0, is it possible to recover the port in use?

If running a fork, how would that work?

var worker = cp.fork('./my-script', {execArgv: ["--inspect=0"]});

Under what mechanism can the port used by the inspector be recovered?

I believe you'd need to set stdio to 'pipe' so that you can get at the output from the fork command. The output will contain the web socket URL, including the port.