[Java] [Benchmarking] Large stdout when running benchmarks

Since ARROW-15058 running the Java benchmarks results in stdout logs that are extremely large (we're seeing them at ~14gb). This is disrupting running benchmarks on conbench.

We've temporarily worked around this by disabling stdout logging entirely, but this will make debugging issues in the future much harder.

Is there any way to reduce the volume of stdout logging when running these benchmarks?

cc @davisusanibar [~fan_li_ya]

**Reporter**: [Elena Henderson](https://issues.apache.org/jira/browse/ARROW-15259) / @ElenaHenderson

_{**Note**: *This issue was originally created as [ARROW-15259](https://issues.apache.org/jira/browse/ARROW-15259). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

El issue no indica ningún archivo fuente, punto de entrada del benchmark ni prueba. Empieza reproduciendo una ejecución de benchmark de Java y siguiendo el registro introducido desde ARROW-15058; compara el volumen de salida con la solución temporal que deshabilita stdout. Se considera completado cuando la salida del benchmark en stdout es sustancialmente menor, se conserva una salida de depuración útil y no se interrumpe conbench.

Escrito por el modelo de indexación a partir del texto del issue.