chore: migrate from base-logging to base-telemetry across spawn

[deer]

build.base.logging (backed by java.util.logging) is being retired in favor of build.base.telemetry, which is designed for end-user-facing diagnostics rather than developer-only log output. This PR replaces every Logger usage in spawn-application, spawn-docker-jdk, spawn-local-jdk, and spawn-local-platform with TelemetryRecorder, and updates each module's pom.xml and module-info.java accordingly.

AbstractTemplatedLauncher and AbstractTemplatedPlatform now expose a TelemetryRecorder -- the launcher gets one via @Inject, consistent with its existing uniqueNameGenerator, diagnostics, and platformContext fields, while the platform constructs one directly from a new TelemetryRecorderFactory constructor parameter (defaulting to SystemTelemetryRecorder::of) and binds it into the injection Context so launchers can pick it up. JsonNodeInputStreamProcessor, JDKDetector, and JDKHomeBasedPatternDetector each gained a TelemetryRecorder-accepting constructor alongside a no-arg convenience constructor that defaults to a PrintStreamTelemetryRecorder writing to System.out/System.err.

Because TelemetryRecorder methods format messages with java.util.Formatter semantics rather than MessageFormat, all {0}-style placeholders were rewritten to %s. JDKHomeBasedPatternDetector.expandPattern and expandGlobPattern also moved from static to instance methods since they now depend on the instance's recorder, which required updating call sites in JDKHomeBasedPatternDetectorGlobExpansionTests and JDKHomeBasedPatternDetectorPruningTests to use a detector instance instead of the class reference.

JDKHomeBasedPatternDetectorLogTests was rewritten to assert against telemetry output via ObservableTelemetryRecorder and NoOpTelemetryRecorder instead of installing a java.util.logging.Handler, removing a previous caveat that the test could pass vacuously if the logging backend changed.