Update chapter09: Align MicroProfile Telemetry content with spec 2.1

[Copilot]

Chapter 09 was written against Telemetry 1.1 and is missing entire signal pillars (metrics, logs) and contains several spec-incorrect configurations. Updates align strictly with the MicroProfile Telemetry 2.1 specification and Eclipse Writing Style Guide.

Spec correctness fixes

• Dependency: 1.1 → 2.1, added required <type>pom</type> (BOM artifact)
• Sampler config: otel.traces.sampler.traceidratio=0.1 → otel.traces.sampler.arg=0.1
• Removed otel.exporter.jaeger.endpoint — not in 2.1 spec; only OTLP is required
• HTTP attribute: http.status_code=500 → http.response.status_code=500 (stabilized HTTP semantic conventions from 2.0)
• Jaeger Docker command: replaced legacy Zipkin/UDP multi-port command with OTLP-native ports (4317/4318)

New content per spec

• Metrics section: Meter CDI injection example + required HTTP server and JVM metrics table (spec-mandated)
• Logs section: explains the log bridge API model — runtimes bridge existing log frameworks; no new Log APIs exposed to applications
• Exporting Telemetry Data: expanded from traces-only to all three signal exporters with correct otel.sdk.disabled=false activation

What's New in MicroProfile Telemetry 2.1

New terminal section covering:

• OpenTelemetry Java upgrade v1.39.0 → v1.48.0
• JVM metrics self-configuration fix (TCK)
• No incompatible changes between 2.0 and 2.1
• Migration path from both 1.1 and 2.0

Minor fixes

• Typo: "Graphana Tempo" → "Grafana Tempo"
• All modified sections marked with // Updated for MicroProfile Telemetry 2.1 using correct AsciiDoc line-comment syntax

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[ttelang]

LGTM