outdated forkNode documentation

[XN137]

Affected version

3.5.5

Bug description

The plugin uses process pipes by default which will be turned to TCP/IP in the version 3.0.0.

https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#forkNode

but the default is still process pipes.

see also https://maven.apache.org/surefire/maven-surefire-plugin/examples/process-communication.html#the-tcp-ip-communication-channel

additionally wondering:
is there a specific reason why the default was not switched i.e. are there known problems with the TCP/IP implementation?
in a brief search i only found #3047 as an open issue.

is it generally supported and recommended to use the TCP/IP variant?
thanks!

[XN137]

@Tibor17 can you maybe help answer some of these questions? thank you