Emit empty additional-tag values on the OTLP stats export path

Aggregation treats an explicitly-empty configured tag ("key:") as a distinct
dimension from an absent one, so it forms a separate aggregate row. The OTLP
writer dropped the empty-value slot, which meant an absent-tag row and an
empty-value row exported identical attribute sets -- two separately-aggregated
points indistinguishable to the backend. Emit the empty value as key="" so the
OTLP attributes stay faithful to the aggregate key; only truly-malformed slots
(no ':' or empty key) are still skipped.

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

Author: dougqh

dd-trace-core/src/main/java/datadog/trace/core/otlp/metrics/OtlpStatsMetricWriter.java

@@ -247,12 +247,14 @@ private void emitDataPointAttributes(
   }
 
   // Splits a packed "key:value" additional-tag string at the first ':' (keys cannot contain ':',
-  // values may) and emits it as an OTLP string attribute. Skips malformed slots (no ':', empty key
-  // or empty value) defensively.
+  // values may) and emits it as an OTLP string attribute. Skips only malformed slots with no ':' or
+  // an empty key. An empty value ("key:") is emitted as key="": the aggregation path treats an
+  // explicitly-empty tag as a distinct dimension from an absent one, so dropping it here would
+  // export two separately-aggregated rows with identical OTLP attribute sets.
   private static void emitAdditionalTag(OtlpMetricVisitor metric, UTF8BytesString additionalTag) {
     String packed = additionalTag.toString();
     int separator = packed.indexOf(':');
-    if (separator <= 0 || separator == packed.length() - 1) {
+    if (separator <= 0) {
       return;
     }
     metric.visitAttribute(