[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 內容生成。