fix: OpenTelemetry instrumentation packages updates

[instanacd]

Changes

• Load @opentelemetry/api from the app root to ensure all instrumentations and monkey patches share the same global API instance.

• Add peer dependency with bounded version range (>=1.3.0 <1.10.0) to enforce compatibility and avoid runtime issues like NonRecordingSpan.

• Updated all @opentelemetry instrumentations versions to latest

What This PR resolves

This PR addresses the multiple API instance issue that occurred when @opentelemetry/api was also installed at the application root. In such cases, our openTelemetry integretion was not functioning correctly before.

When the OTEL SDK and our collector are used together within the same application:

• If the OTEL SDK is initialized first, it now correctly captures all our instrumented libraries (including our OTEL). Previously, this was not happening. OTEL also works.

• If our collector is initialized first, it currently blocks OTEL tracing - this is a known issue and will be addressed separately.

This PR resolves the multiple instance problem. Tests demonstrating OTEL SDK and our collector behaviors will be included in a separate PR.

There is still issue when our collector initialized first.

References:

https://github.com/open-telemetry/opentelemetry-js/issues/4832
open-telemetry/opentelemetry-js#5454
https://jsw.ibm.com/browse/INSTA-59002

[kirrg001]

Still compatible with Node v18 and with Otel API version >=1.3.

[aryamohanan]

A few tests are failing, specifically, the ones that assert fs spans. The issue noticed after the recent update, where the otel fs package was installed at the root level, leading to a conflict between different OpenTelemetry API instances.

Root Cause: Multiple OTEL API instances are being loaded that intercept the tracing

Working case: When modules are loaded from the same location (packages/core/node_modules), both the core code and the FS instrumentation share a single OTEL API instance. As a result, spans are created correctly.

Non-working case: When the FS instrumentation is loaded from a different location (e.g., root node_modules), it uses a separate OTEL API instance. Since our core code applies monkey patches to its own API instance(packages/code/node_modules), the instrumentation does not receive those patches, causing spans to be missing and tests to fail.

[aryamohanan]

Known Issues

• OpenTelemetry API version compatibility:
  If a customer installs @opentelemetry/api with a version below v1.3.0, tracing will not function correctly.
  In such cases, installing v1.3.0 at the project root and v1.9.0 (latest) in our directory, the issue due to mismatched API instances and incomparable version
  Generally, this is not a valid setup since versions below v1.3.0 are incompatible with most OpenTelemetry instrumentations.

• OpenTelemetry SDK + Instana initialization order:
  When both OpenTelemetry SDK and Instana are used together, and our collector is initialized first, tracing fails to work.
  This is a known limitation and needs to be addressed separately.

• AsyncHooksContextManager usage:
  The current use of AsyncHooksContextManager should be revisited. It may not be applied correctly or could be irrelevant in the existing setup.

[kirrg001]

Great work <3

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[kirrg001]

Super sweet