Feature: provide memory usage statistics for processes spawned by Gradle

[lwasyl]

It would be insanely helpful to understand how to optimize the build — how many workers to use, how much memory to assign to e.g. Test tasks, and to understand why Gradle daemon disappears (which is usually a sign of OOM).

One tricky thing would be attaching to processes like Kotlin compile daemon (or Gradle daemon itself) which aren't necessarily created by Gradle, but which are part of the build anyway

[janbarari]

Hey @lwasyl
Thank you for submitting your request.
Since the plugin is an analytics tool. It won't tell you what to do. But, regarding the workers and memory. It would be nice to have a metric to see the current workers that active in the build process or the memory usage. I consider that in my investigation for the next milestone.