Configure Span Pipeline for BedrockAgentCore

[yiyuan-he]

What does this pull request do?

Configures span pipeline for BedrockAgentCore to send traces to OTLP X-Ray endpoint when AGENT_OBSERVABILITY_ENABLED is enabled. We also pass an instance of logger_provider to our custom OTLP Span Exporter since we may need to emit input/output responses to the logs pipeline.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[thpierce]

Overview is a bit confusing. The only thing we are doing is: If flag set, add the default logger provider to span exporter. The overview links to https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-events/ as justificaiton for this change, but that page does not mention log anywhere.

In short: I don't know why we are making this change.

[yiyuan-he]

Overview is a bit confusing. The only thing we are doing is: If flag set, add the default logger provider to span exporter. The overview links to https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-events/ as justificaiton for this change, but that page does not mention log anywhere.

In short: I don't know why we are making this change.

Upstream OTel has decided for input/output prompt data in Spans, they will split it into events (which are really just logs with a format that OTel can make guarantees about). The reason we need to add a logger provider to the Span pipeline is to split the input/output prompt data from the spans in our OTLPAwsSpanExporter and send to the logs pipeline.

[mxiamxia]

Overview is a bit confusing. The only thing we are doing is: If flag set, add the default logger provider to span exporter. The overview links to https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-events/ as justificaiton for this change, but that page does not mention log anywhere.
In short: I don't know why we are making this change.

Upstream OTel has decided for input/output prompt data in Spans, they will split it into events (which are really just logs with a format that OTel can make guarantees about). The reason we need to add a logger provider to the Span pipeline is to split the input/output prompt data from the spans in our OTLPAwsSpanExporter and send to the logs pipeline.

Left a comment to the lines of code where I think we can add a high level explanations why logger provider is needed agent case,