Fix surefire corrupted channel

Testing, at least with hbase-server, emits a warning,

[WARNING] Corrupted channel by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-5036/yetus-jdk8-hadoop2-check/src/hbase-server/target/surefire-reports/2023-03-14T13-20-30_932-jvmRun1.dumpstream

I cannot tell if this is causing maven to recognize the test run as a failure, though in this case, the test run was marked as failing, with two tests rerun and passing on their second attempt.

Surefire apparently uses stdio to communicate with maven, so when our code under test produces output on the channel, it corrupts that communication.

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