Enable concurrent execution of the utility analyzers

[csaba-sagi-sonarsource]

Fixes #6674

I opted for ConcurrentBag as it had the best performance ( scenario: multiple threads writing, and a single consumer writing to disk after the threads finished their job).
Results of the benchmark:

ConcurrentStack | ConcurrentQueue | SynchronizedStream | ConcurrentBag
455.93 ms | 438.83 ms | 327.23 ms | 221.9 ms

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[csaba-sagi-sonarsource]

It is a draft, as I did not yet have time to check if enabling concurrent execution actually improved the performance or not.

[costin-zaharia-sonarsource]

This will increase the thread contention even more, accentuating the problems were not facing. This needs to be measured on projects of different sizes and only after that take a decision.

[mary-georgiou-sonarsource]

Closing this PR for now - its goal was to fix the performance introduced (see here) but it did not really help. As the issue connected to this PR still has value to improve performance, it should stay in the backlog and be handled in a future sprint.