fix(test): Clean up global Sentry state in SentryPropagatorTest

SentryPropagatorTest calls Sentry.init with strict trace continuation
but never closes Sentry afterward. This leaks global state into
SentrySpanProcessorTest where SentryPropagator uses the global
ScopesAdapter and rejects incoming sentry-trace headers under the
leaked strict mode configuration.

Add @AfterTest that calls Sentry.close() to prevent state leakage.

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

Author: adinauer

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

@@ -5,6 +5,7 @@ import io.opentelemetry.context.Context
 import io.sentry.Sentry
 import io.sentry.opentelemetry.SentryOtelKeys.SENTRY_BAGGAGE_KEY
 import io.sentry.opentelemetry.SentryOtelKeys.SENTRY_TRACE_KEY
+import kotlin.test.AfterTest
 import kotlin.test.BeforeTest
 import kotlin.test.Test
 import kotlin.test.assertFalse
@@ -17,6 +18,11 @@ class SentryPropagatorTest {
     Sentry.init("https://key@sentry.io/proj")
   }
 
+  @AfterTest
+  fun teardown() {
+    Sentry.close()
+  }
+
   @Suppress("DEPRECATION")
   @Test
   fun `ignores incoming headers when strict continuation rejects org id`() {