Explicitly define processors that drop the client context

[dmitryax]

We have a few processors that drop client metadata (context), which potentially can carry important authentication data that exporters are supposed to use.

It's important to clearly document the processors dropping the context. Can be done in metadata.yaml as another warning added to https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/standard-warnings.md#unsound-transformations.

Action items

1. Identify processors dropping the context
2. Fix those that drop it unintentionally
3. Document those that drop it intentionally

[Neema-Joju]

Hi,
May I work on this issue?
It would be my first time contributing to this repo.
Thanks

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.