fix(telemetry): resolve otel-naming and UBSAN CI failures

- Add job_type to otel-naming builtins (standard Prometheus label for
  job-queue metrics used in node-health dashboard)
- Add OpenTelemetry SDK to UBSAN suppressions (intentional unsigned
  integer overflow in attributemap_hash.h hash computation)

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

.github/scripts/otel-naming/check_otel_naming.py

@@ -814,6 +814,7 @@ def run_rule_d_dashboards(
         "service_version",
         "service_instance_id",
         "job",
+        "job_type",  # standard Prometheus label for job-queue metrics
         "instance",
     }
     # A dashboard label is valid if it is a span attribute (L1), a native-metric

sanitizers/suppressions/ubsan.supp

@@ -102,6 +102,10 @@ undefined:nudb
 # Snappy compression library intentional overflows
 unsigned-integer-overflow:snappy.cc
 
+# OpenTelemetry SDK intentional overflows in hash functions
+unsigned-integer-overflow:opentelemetry/sdk/common/attributemap_hash.h
+unsigned-integer-overflow:opentelemetry
+
 # Abseil intentional overflows in hashing, RNG and time arithmetic.
 # Matched at library scope (like boost above): the wraparound is by design
 # across many absl files (hash mixing, raw_hash_set probing, duration math,