ReportAnalyzer should report when analyzers don't support concurrent execution #82480
Description
Got a trace from a partner team which indicates a lot of time spent on lock contention in AnalyzerExecutor. This leads us to think that there could be a bottleneck with an analyzer that doesn't enable concurrent execution. We have a binlog which includes ReportAnalyzer, but the data doesn't appear to indicate which analyzers enabled concurrent execution or not.
This data feels relevant for users investigating build perf issues. Let's add this information to the report.