Add OpenTelemetry tracing and log export via OTLP

Shared telemetry init module in compliance-core (behind `telemetry` feature)
sets up OTLP/gRPC export for traces and logs when OTEL_EXPORTER_OTLP_ENDPOINT
is set. Falls back to console-only output when unset.

Both agent and dashboard now use the shared init. Docker Compose includes
an OTel Collector service with a config template for SigNoz, Grafana
Tempo/Loki, Jaeger, etc.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

bin/main.rs

@@ -2,10 +2,9 @@
 
 #[allow(clippy::expect_used)]
 fn main() {
-    dioxus_logger::init(tracing::Level::DEBUG).expect("Failed to init logger");
-
     #[cfg(feature = "web")]
     {
+        dioxus_logger::init(tracing::Level::DEBUG).expect("Failed to init logger");
         dioxus::web::launch::launch_cfg(
             compliance_dashboard::App,
             dioxus::web::Config::new().hydrate(true),
@@ -14,6 +13,10 @@ fn main() {
 
     #[cfg(feature = "server")]
     {
+        dotenvy::dotenv().ok();
+        let _telemetry_guard =
+            compliance_core::telemetry::init_telemetry("compliance-dashboard");
+
         compliance_dashboard::infrastructure::server_start(compliance_dashboard::App)
             .map_err(|e| {
                 tracing::error!("Unable to start server: {e}");