[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.*}

A issue não indica um arquivo-fonte, um ponto de entrada de benchmark ou um teste. Comece reproduzindo uma execução de benchmark em Java e rastreando o logging introduzido desde ARROW-15058; compare o volume de saída com a solução temporária que desabilita stdout. Considera-se concluído quando a saída do benchmark em stdout for substancialmente menor, mantendo uma saída de debugging útil e sem interromper o conbench.

Escrita pelo modelo de indexação a partir do texto da issue.