fix(opentelemetry): Fix reversed fallback logic in getTraceData

The fallback condition in getTraceData was reversed, making the scope
context path unreachable dead code. api.trace.setSpan() always returns
a truthy Context object, so placing it first in the OR expression
meant the fallback (scope && getContextFromScope(scope)) could never
be evaluated.

This fix restores the correct order: check scope context first, then
fall back to setSpan if the scope doesn't exist.

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

Author: cursoragent

packages/opentelemetry/src/utils/getTraceData.ts

@@ -24,7 +24,7 @@ export function getTraceData({
   if (span) {
     const { scope } = getCapturedScopesOnSpan(span);
     // fall back to current context if for whatever reason we can't find the one of the span
-    ctx = api.trace.setSpan(api.context.active(), span) || (scope && getContextFromScope(scope));
+    ctx = (scope && getContextFromScope(scope)) || api.trace.setSpan(api.context.active(), span);
   }
 
   const { traceId, spanId, sampled, dynamicSamplingContext } = getInjectionData(ctx, { scope, client });