[SUREFIRE-1801] New TCP communication mode defers "Listening for transport" debug message

**[Falko Modler](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=famod)** opened **[SUREFIRE-1801](https://issues.apache.org/jira/browse/SUREFIRE-1801?redirect=false)** and commented

When using

```xml

```

and `-Dmaven.surefire.debug` you see the message

```
Listening for transport dt_socket at address: 5005
```

_only after_ you have connected the debugger, which defeats the whole point of this message and leaves the user under the impression that test execution is stuck before opening the debug port.

In "legacy" mode the message is displayed as expected (before connecting the debugger).

---

**Affects:** 3.0.0-M5

**Issue Links:**
- [SUREFIRE-1881](https://issues.apache.org/jira/browse/SUREFIRE-1881) Java agent printing to native console makes build block when using SurefireForkNodeFactory

Start by reproducing the issue with SurefireForkNodeFactory, -Dmaven.surefire.debug, and the XML forkNode configuration, then compare the output with legacy mode. Done means the "Listening for transport dt_socket at address: 5005" message appears before the debugger connects, rather than afterward.

Written by the indexing model from the issue text.