[load-generator] Update locustfile for logging with TraceContext

[ps48]

Changes

• Added LoggingInstrumentor: This is an addition that automatically injects trace context (trace_id, span_id) into all log records.
• Reorganized initialization order: Moved the tracer provider before the logger provider to ensure trace context is available.
• Added consistent Resource: Used the same resource across all telemetry signals for better correlation.
• Wrapped tasks in spans: Each task method now creates a span, which provides trace context for any logs within that span.
• Added explicit logging: Added log statements within spans so you can see the trace context in action.
• Added span attributes: Added relevant attributes to spans for better observability.

Related issue: #2250

Merge Requirements

For new features contributions, please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs
• Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

[julianocosta89]

Hey @ps48 thanks for taking care of that.

I've left some comments, basically to remove the resource and rely on the service name coming from the env var, and asking to keep just one log entry per call.

Just to not explode the amount of data produced by the load-gen.

[julianocosta89]

Let's rely on the env var for that:
https://github.com/open-telemetry/opentelemetry-demo/blob/main/docker-compose.yml#L421C7-L421C41

[ps48]

Makes sense removed the resource attribute injection.

[julianocosta89]

All the new spans already increased a lot the amount of data leaving the load-gen service, let's keep just one log entry per call.

[ps48]

Sure, just kept the final log statement for each entry. db6f18a

[ps48]

Hi @julianocosta89, this commit db6f18a should address all the mentioned changes.