fix(otel): Map messaging "settle" to queue.settle

OTel messaging semconv defines messaging.operation.type=settle for
consumer ack/nack/reject spans (JMS, RabbitMQ, Pulsar acknowledge).
The switch had no case for "settle", so settle spans on
SpanKind.CONSUMER were falling through to the SpanKind fallback and
becoming queue.process — duplicating the real process span — while
on SpanKind.CLIENT they became the generic "queue" default.

queue.settle is one of the canonical Queues telemetry ops per
https://develop.sentry.dev/sdk/telemetry/traces/modules/queues/, so
add the explicit mapping.

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

Author: adinauer

sentry-opentelemetry/sentry-opentelemetry-core/src/main/java/io/sentry/opentelemetry/SpanDescriptionExtractor.java

@@ -136,6 +136,8 @@ private OtelSpanInfo descriptionForMessagingSystem(final @NotNull SpanData otelS
         case "process":
         case "deliver":
           return "queue.process";
+        case "settle":
+          return "queue.settle";
         default:
           // fall through to SpanKind mapping
           break;

sentry-opentelemetry/sentry-opentelemetry-core/src/test/kotlin/SpanDescriptionExtractorTest.kt

@@ -316,6 +316,23 @@ class SpanDescriptionExtractorTest {
     assertEquals(TransactionNameSource.TASK, info.transactionNameSource)
   }
 
+  @Test
+  fun `maps messaging settle operation type to queue settle op`() {
+    givenAttributes(
+      mapOf(
+        MessagingIncubatingAttributes.MESSAGING_SYSTEM to "rabbitmq",
+        MessagingIncubatingAttributes.MESSAGING_DESTINATION_NAME to "my-queue",
+        MessagingIncubatingAttributes.MESSAGING_OPERATION_TYPE to "settle",
+      )
+    )
+
+    val info = whenExtractingSpanInfo(queueTracingEnabled = true)
+
+    assertEquals("queue.settle", info.op)
+    assertEquals("my-queue", info.description)
+    assertEquals(TransactionNameSource.TASK, info.transactionNameSource)
+  }
+
   @Test
   fun `falls back to legacy messaging operation attribute`() {
     @Suppress("DEPRECATION")