Use Jackson for telemetry files

[jaydeluca]

Fixes some parsing issues related to some of the kafka metric descriptions, which needed to be escaped. Rewrote the class that writes the .telemetry files to use jackson.

This was the error being fixed:

at [Source: (StringReader); line: 120, column: 61] (through reference chain: io.opentelemetry.instrumentation.docs.internal.EmittedMetrics["metrics_by_scope"]->java.util.ArrayList[0]->io.opentelemetry.instrumentation.docs.internal.EmittedMetrics$MetricsByScope["metrics"]->java.util.ArrayList[14])
Nov 16, 2025 2:24:50 AM io.opentelemetry.instrumentation.docs.parsers.EmittedMetricsParser lambda$parseAllMetricFiles$1
SEVERE: Error parsing metrics file (/home/runner/work/opentelemetry-java-instrumentation/opentelemetry-java-instrumentation/instrumentation/kafka/kafka-clients/kafka-clients-0.11/.telemetry/metrics-6309e954-0e9b-46e3-a896-04d2754a39a4.yaml): mapping values are not allowed here
in 'reader', line 120, column 61:
... rage lead of the partition. Note: For topic names with periods ( ...
^

[jaydeluca]

opentelemetry-java-instrumentation/instrumentation/kafka/kafka-streams-0.11/javaagent/src/test/java/io/opentelemetry/javaagent/instrumentation/kafkastreams/KafkaStreamsDefaultTest.java

Line 69 in 0e7a006

Span.current().setAttribute("asdf", "testing");

[trask]

I'm not sure if we should document telemetry that comes from metric bridges like kafka and micrometer?