Output lsof information on suspected leakage

[ahus1]

Closes #5944

Motivation:

Show lsof information when the test fails to allow an analysis of what files changes.

Example output:

lsof before:
COMMAND    PID     USER   FD   TYPE             DEVICE  SIZE/OFF     NODE NAME
java    791300 aschwart  cwd    DIR               0,41        32 21285744 /home/aschwart/redhat/workspace/vert.x/vertx-core
java    791300 aschwart  rtd    DIR               0,37       266      256 /
java    791300 aschwart  txt    REG               0,41     12984 20643956 /home/aschwart/.jdks/corretto-17.0.17/bin/java
...

lsof after:
COMMAND    PID     USER   FD   TYPE             DEVICE  SIZE/OFF     NODE NAME
java    791300 aschwart  cwd    DIR               0,41        32 21285744 /home/aschwart/redhat/workspace/vert.x/vertx-core
java    791300 aschwart  rtd    DIR               0,37       266      256 /
java    791300 aschwart  txt    REG               0,41     12984 20643956 /home/aschwart/.jdks/corretto-17.0.17/bin/java
...

[vietj]

how does such failure handling work on windows ?

[ahus1]

@vietj - the detection logic of a leak is still identical. The only change in this PR is to augment the information on failure.

So the behavior of failing/not failing is as before. But when you run on Linux, it will show you the full lsof output and you might be closer to understand why this failed. On Windows and everywhere such a CLI is not available, the output would just be skipped.

[ahus1]

This has run stale and acquired conflicts. Closing.