Extract node-fetch non-span functionality into standalone instrumentation

[mydea]

Description

Today, we still rely on adding the @opentelemetry/instrumentation-undici for all users, even if they have performance disabled.

We should change this like we already did for http here: #13763

So that we have our own instrumentation, that registers our own diagnostics channel stuff, to ensure we have 1. trace propagation 2. breadcrumbs. This way, we can stop adding the instrumentation-undici instrumentation from OTEL, reducing one more dependency/potential for conflict.

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #15231, which was included in the 9.1.0 release.