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

该 issue 没有指出源文件、基准测试入口或测试。首先重现一次 Java 基准测试运行，并跟踪自 ARROW-15058 以来引入的日志记录；将输出量与临时禁用 stdout 的 workaround 进行比较。完成的标准是：基准测试的 stdout 输出大幅减少，同时保留有用的调试输出，并且不影响 conbench。

由索引模型根据 Issue 内容生成。