feat: add support for mapping s3 bucket prefix to OTel resource attributes

[yshengli]

Description

Introduced the resource_attrs_to_s3/s3_prefix configuration field to enable mapping the S3 bucket prefix to an OpenTelemetry resource attribute. When this field is set, the S3 prefix is determined by the specified resource attribute, with s3uploader/s3_prefix used as a fallback if the attribute is missing or empty.

Link to tracking issue

Fixes #37858

Testing

• Added unit tests to verify the functionality of the related code changes
• Built the OpenTelemetry Collector locally to ensure the component behaves as intended

Documentation

Updated the README to document the new configuration field:

• Described its impact on the component’s behavior
• Clarified how it interacts with the s3uploader/s3_prefix setting
• Included an example demonstrating how to use it

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: yshengli / name: Yongsheng Li (4aa9871, 6656f2b, 93442d3, d1d81da, 7bcea80, f172045, ad11c5b)

[Erog38]

One change I ask is around choosing which attribute to map, and using both resource as well as metric, log, and span attributes.

Other than that, nice work!

[atoulme]

One change I ask is around choosing which attribute to map, and using both resource as well as metric, log, and span attributes.

Other than that, nice work!

I don't think that's needed. You'd use the groupbyattrs processor earlier in the pipeline to group your incoming data. This way you can make the data map to a nice payload.

[atoulme]

Please address the failing CI.