Issue with multiple TelemetryClients running in same Node.js process not respecting configurations

OpenTelemetry behind the scenes have a lot of global handling, including providers, context and instrumentation attaching, this is causing inconsistencies in specific environments where multiple SDK instances are running in same Node.js process, causing issue like dependency/exception capturing even if explicitly configured off.