fix(tracing): upgrade to Otel 2.0+

[MichaelDoyle]

Key Changes:

1. Core Telemetry Fixes (js/core)

   • Initialization Race Condition: Updated enableTelemetry in tracing.ts to correctly store and await the actual initialization promise. This prevents spans from being created before the SDK is fully ready.
   • Improved Test Reliability: Added await flushTracing() to beforeEach and relevant test cases in action_test.ts and flow_test.ts. This ensures all asynchronously emitted spans are captured before assertions are made.
   • Version-Agnostic Span Processing: Implemented a MultiSpanProcessor in node-telemetry-provider.ts to reliably handle multiple span processors across different OpenTelemetry versions.
   • SDK Re-initialization: Refined the enableTelemetry logic to properly shut down existing SDK instances before re-initializing, avoiding duplicate instrumentation and resource leaks.

2. OpenTelemetry 2.0 Compatibility (js/plugins/google-cloud)

   • Traces Test: Updated traces_test.ts to use parentSpanContext?.spanId instead of the deprecated parentSpanId property, which was removed in OTel 2.0.
   • Metrics Test:
     • Updated metrics_test.ts to use the InstrumentType enum for metric type comparisons.
     • Addressed the removal of the type property from the MetricDescriptor interface.

Checklist (if applicable):

• PR title is following https://www.conventionalcommits.org/en/v1.0.0/
• Tested (manually, unit tested, etc.)
• Docs updated (updated docs or a docs bug required)

AIM

Dev UI