Detect compilation during measurement phase in runtime-benchmarks

[Akirathan]

#10574 introduced detection of compilation during benchmarking for std-benchmarks. We need something similar for benchmarks in runtime-benchmarks. #10574 modifies the code that is generated by the BenchProcessor annotation processor that generates the code for all the JMH benchmarks for stdlibs. In runtime-benchmarks, we are writing all this code ourselves. Therefore, the diff of #10574 cannot be simply used for this. We need to think about how to enable the engine logs and detect these messages for all the benchmarks in runtime-benchmarks without the need to modify them all.

Related:

• Speed benchmarks up by shortening the 10s iteration time #6271