fix: refactor process collection to a shared kotlin process collector

[cdsap]

Summary

Problem

Kotlin process discovery is duplicated in two infrastructure paths: src/main/kotlin/io/github/cdsap/kotlinprocess/InfoKotlinProcessBuildService.kt:21-27 consolidates jstat/jinfo provider output for console reporting, while src/main/kotlin/io/github/cdsap/kotlinprocess/DevelocityWrapperConfiguration.kt:33-38 repeats the same ConsolidateProcesses().consolidate(..., TypeProcess.Kotlin) call for Build Scan reporting.

Why this matters

The core behavior of turning jstat/jinfo output into Kotlin process data is coupled to both Gradle BuildService lifecycle code and Develocity integration code. Any future change to process parsing, filtering, or error handling must be made in multiple places and is harder to test without exercising Gradle or Develocity wiring.

Proposed change

Introduce a small core helper, for example KotlinProcessCollector, that accepts jstat and jinfo strings and returns List<Process> using the existing ConsolidateProcesses call. Update InfoKotlinProcessBuildService and DevelocityWrapperConfiguration to resolve their providers as they do today, then delegate only the consolidation step to this helper.

Notes

From a clean architecture lens, this extracts the small domain operation, collecting Kotlin process facts from raw tool output, away from Gradle BuildService and Develocity adapter code while preserving the repository's current simple class-based style.

Fixes #88

Changes

• src/main/kotlin/io/github/cdsap/kotlinprocess/DevelocityWrapperConfiguration.kt
• src/main/kotlin/io/github/cdsap/kotlinprocess/InfoKotlinProcessBuildService.kt
• src/main/kotlin/io/github/cdsap/kotlinprocess/KotlinProcessCollector.kt
• src/test/kotlin/io/github/cdsap/kotlinprocess/KotlinProcessCollectorTest.kt

Verification

• ./gradlew ktlintCheck
• ./gradlew test