Description

As prework to #14332 we want to do multiple things:

• Add a openTelemetryInstrumentations option to Sentry.init() and NodeClient as an alternative and migration path for the foot-gunny Sentry.addOpenTelemetryInstrumentation() (feat(node): Add openTelemetryInstrumentations option #14484)
• Deprecate registerEsmLoaderHooks.include and registerEsmLoaderHooks.exclude in favor of using onlyIncludeInstrumentedModules: true and add a note to registerEsmLoaderHooks and all of its "object options" explaining that in the future the SDK will only wrap modules that there are OTEL instrumentations registered for. (feat: Deprecate registerEsmLoaderHooks.include and registerEsmLoaderHooks.exclude #14486)
• Adjust docs to recommend using the openTelemetryInstrumentations option instead of addOpenTelemetryInstrumentation and adjust docs to recommend always setting registerEsmLoaderHooks: false and registering their own loader hooks if a complete custom OTEL setup is used. (Guide towards v9 for ESM OTEL setups sentry-docs#11974)
• Deprecate addOpenTelemetryInstrumentation (feat: Deprecate addOpenTelemetryInstrumentation #14485)