Instrument pipeline mechanisms with OTEL tracing and metrics to allow related insights and analysis

[dadrus]

Preflight checklist

• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines."
• [X] I have discussed this feature request with the community.

Describe the background of your feature request

per-rule tracing and metrics data could be quite useful for tracking down slow pipelines on a per request basis

Describe your idea

As the title says, instrument the pipeline mechanisms to allow related insights and analysis

Are there any workarounds or alternatives?

Indirect analysis is possible in a limited way by substracting the time measured for outbound connections opened by a particular mechanism.

Version

v0.11.1-alpha

Additional Context

Discussed in Discord: https://discord.com/channels/1100447190796742698/1146494243985166376/1146494243985166376