Disable the stream_unique metric attribute at Detailed level (#119)

This field has caused a (predictable) cardinality explosion in our
internal pipeline monitoring setup. This leaves the feature in but
disabled at Detailed level. While the collectorconfig package won't
parse a value greater than Detailed, callers can still pass `Detailed+1`
to enable.

pkg/otel/arrow_record/consumer.go

@@ -91,7 +91,8 @@ type Consumer struct {
 	memoryCounter metric.Int64UpDownCounter
 
 	// uniqueAttr is set to an 8-byte hex digit string with
-	// 32-bits of randomness, applied to all metric events.
+	// 32-bits of randomness, applied to all metric events
+	// when MetricsLevel is > Detailed (i.e., above detailed).
 	uniqueAttr attribute.KeyValue
 }
 
@@ -191,7 +192,7 @@ func (c *Consumer) metricOpts(kvs ...attribute.KeyValue) []metric.AddOption {
 	if c.metricsLevel < configtelemetry.LevelNormal {
 		return nil
 	}
-	if c.metricsLevel == configtelemetry.LevelDetailed {
+	if c.metricsLevel > configtelemetry.LevelDetailed {
 		kvs = append(kvs, c.uniqueAttr)
 	}
 	return []metric.AddOption{