Revert "feat(sdk-trace-node): support xray propagator (#4602)"

[pichlermarc]

This reverts commit 75d88f7.

Which problem is this PR solving?

According to the specification, we MUST NOT maintain the aws and aws-lambda propagators as part of the core repo, therefore we also cannot have it be a dependency of @opentelemetry/sdk-trace-node.

Therefore this PR reverts #4602 (unreleased)

To replace this feature, I plan to introduce a getPropagator() function, which uses OTEL_PROPAGATORS to build a propagator based on its value, see open-telemetry/opentelemetry-js-contrib#2232

[trentm]

Oof. Does this mean that the @opentelemetry/propagator-aws-xray pacakge should move back to the contrib repo?

[JamieDanielson]

Linking for posterity, since I found myself looking for it and others may as well. We had suggested as a follow-up to reconsider the spec guidelines for xray and it was rejected. The getPropagators option sounds like the best move forward anyway.

[pichlermarc]

Oof. Does this mean that the @opentelemetry/propagator-aws-xray pacakge should move back to the contrib repo?

Yes, that'd be the next step. We can transfer it back to the contrib repo, and we'd have to do the same to @opentelemetry/propagator-aws-xray-lambda and then we're spec compliant again. Looking at it from a long-term perspective, adding all propagators to the @opentelemetry/sdk-trace-node package was not going to be a sustainable solution.

The proposed approach above comes a bit closer to what I think we should do in the future (full separation of env var configuration from core SDK packages (sdk-metrics, sdk-logs, sdk-trace) into an autoconfigure component)