Allow users to decide whether to start a new OpenTelemetry trace for delayed messages

[mauroservienti]

Describe the suggested improvement

Is your improvement related to a problem? Please describe.

Currently, NServiceBus always starts a new trace for a delayed message (#7049). Under the hood, the new trace is linked to the parent one; however, the trace appears broken if the chosen visualization tool does not support OpenTelemetry links (at the moment, only Azure AppInsights supports them). It is challenging for users to reconcile things. This decision has been made to better support sampling scenarios. Otherwise, the sample would have always been truncated when using a delayed message.

Describe the suggested solution

It would be helpful to allow users to decide whether to start a new OpenTelemetry trace for delayed messages. If a user is not interested in OpenTelemetry sampling capabilities and is using one of the many tools that don't support OpenTelemetry links, they could opt-in to not start a new trace by default.

Additional Context

No response