feat(v8): Remove autoDiscoverNodePerformanceMonitoringIntegrations

[AbhiPrasad]

• Remove autoDiscoverNodePerformanceMonitoringIntegrations
• Remove lazyLoadedNodePerformanceMonitoringIntegrations
• Delete all old tracing integrations other than Express, which will be addressed separately (see OpenTelemetry Express instrumentation does not match Sentry instrumentation #10168 for more details).

ref #9885

[mydea]

Hmm is it OK to delete the integrations yet? Don't we need them in metaframeworks still, I wonder (e.g. http instrumentation etc. in next/remix/etc)?

[AbhiPrasad]

All of these integrations should be safe to delete, everything else lives in node/core as appropriate. Only exception is express, as highlighted in the issue.

[mydea]

OK, just to clarify: So e.g. next/remix/astro do not use/depend on the DB integrations? Does that not mean you cannot e.g. instrument your mysql usage in the server side of next/remix/... anymore then?

Maybe this is fine - I've also looked into deleting this, which would help us quite a bit, but held off so far because I thought we'd still need this for the time being 😅

[AbhiPrasad]

So e.g. next/remix/astro do not use/depend on the DB integrations

Ahhh I see what you mean. All of these are optional, but given we haven't converted the packages to use otel this does mean it will break for some.

I'll draft for now, we can come back to this!