fix: refactor kotlin process collection to a shared core component

[cdsap]

Summary

Problem

src/main/kotlin/io/github/cdsap/kotlinprocess/InfoKotlinProcessBuildService.kt and src/main/kotlin/io/github/cdsap/kotlinprocess/DevelocityWrapperConfiguration.kt both directly instantiate ConsolidateProcesses and know that the parser must use TypeProcess.Kotlin. That duplicates core Kotlin-process collection behavior inside two delivery paths: console reporting and Develocity reporting.

Why this matters

Keeping the collection rule embedded in infrastructure adapters makes future parser changes easier to apply inconsistently and makes the reporting paths harder to test independently from process consolidation.

Proposed change

Introduce one small shared component, for example KotlinProcessCollector, that accepts the jStat and jInfo providers or raw strings and returns the consolidated Kotlin Process list. Update both console and Develocity paths to call it, preserving current output and Build Scan values.

Notes

From a clean architecture lens, process collection is core behavior while console output and Develocity Build Scan publishing are adapters. This refactor keeps the boundary small without changing public plugin behavior.

Fixes #82

Changes

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

Verification

• ./gradlew ktlintCheck
• ./gradlew test