IDEA-358562 Fix build output 'Starting Daemon' event using Daemon JVM criteria

[vmadalin]

Context

The Daemon toolchain was introduced in Gradle 8.8 and the motivation behind it and other technical details can be found on the public spec document. The implementation follows the agreed details on spec document and UI/UX document.

Summary

Given a project using Daemon JVM criteria when starting a daemon the event is captured multiple times on GradleProgressListener due to the fact that a new ProgressLoggerFactory.newOperation was nested on the original Starting Gradle Daemon as part of Daemon toolchain implementation. However, Gradle triggers always the parent event on completion resulting on the following:

Build
Starting Gradle Daemon
Discovering toolchains
Starting Gradle Daemon
Connecting to Gradle Daemon
Starting Gradle Daemon
Build

Before we had only Connecting to Gradle Daemon expecting only 2 Starting Gradle Daemon events, however, this isn't longer the case. For this reason, until a better way is provided by Gradle we are going to relay on the fact that latest Starting Gradle Daemon is always proceeded by Build, representing his parent.

Reported Gradle issue: gradle/gradle#31777

Tests

• GradleOutputParsersMessagesImportingTest.kt

Overview