fix: refactor process collection to centralize provider materialization

[cdsap]

Summary

Problem

InfoKotlinProcessBuildService.close and DevelocityWrapperConfiguration.buildScanDevelocityReporting both independently read jStat/jInfo providers and invoke KotlinProcessCollector, duplicating the infrastructure-to-domain handoff.

Why this matters

The duplicated boundary can drift between console and Build Scan reporting, while tests must inspect adapter implementation details to ensure consistent collection behavior.

Proposed change

Add one internal helper beside KotlinProcessProviders that materializes both providers and delegates to KotlinProcessCollector, then use it from both reporting adapters. Preserve KotlinProcessCollector's raw-string API and all output behavior.

Notes

This keeps provider access in the infrastructure-facing consolidation boundary while leaving raw process parsing in the core collector, reducing coupling without introducing a broader abstraction.

Fixes #144

Changes

• plugin/src/main/kotlin/io/github/cdsap/kotlinprocess/DevelocityWrapperConfiguration.kt
• plugin/src/main/kotlin/io/github/cdsap/kotlinprocess/InfoKotlinProcessBuildService.kt
• plugin/src/main/kotlin/io/github/cdsap/kotlinprocess/KotlinProcessConsolidation.kt
• plugin/src/test/kotlin/io/github/cdsap/kotlinprocess/KotlinProcessCollectorOwnershipTest.kt
• plugin/src/test/kotlin/io/github/cdsap/kotlinprocess/KotlinProcessConsolidationTest.kt

Verification

• ./gradlew ktlintCheck
• ./gradlew test