Docs: clarify why we currently prefer X-Ray over ADOT in Tracer

[dreamorosi]

What were you searching in the docs?

In the Tracer docs, when introducing the utility, we should clarify why we use X-Ray over ADOT/OTEL - which appears to be the recommended way of tracing functions by other AWS teams. The Python docs for Tracer have a banner that explains the reasoning, and since it's a somewhat common question from customers we should add the same banner.

Is this related to an existing documentation section?

https://docs.powertools.aws.dev/lambda/typescript/latest/core/tracer/#installation

How can we improve?

We should add a banner similar to the one present in the Python docs that specifies that we use X-Ray for latency reasons, see here: https://docs.powertools.aws.dev/lambda/python/latest/core/tracer/#getting-started

Got a suggestion in mind?

!!! note "Tracer relies on AWS X-Ray SDK over [OpenTelememetry Distro (ADOT)](https://aws-otel.github.io/docs/getting-started/lambda){target="_blank"} for optimal cold start (lower latency)."

Acknowledgment

• I understand the final update might be different from my proposed suggestion, or refused.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v1.11.1 version!