[BUG] Since release 3.2.0 there are CSP violations attempting to connect to js.monitor.azure.com (using npm not snippet)

**Description/Screenshot**

Since updating to 3.2.0 we are now getting CSP violations connecting to js.monitor.azure.com. This was not happening in 3.1.2. We are using npm and the javascript initialization, not the snippet because we have a policy of not loading scripts from external domains.

**Steps to Reproduce**

- OS/Browser: Windows 11/Chrome 124
- SDK Version [e.g. 22]: 3.2.0
- How you initialized the SDK:

using npm package

const appInsights = new ApplicationInsights({
config: { instrumentationKey: appInsightsKey, disableCookiesUsage: true },
})
appInsights.addTelemetryInitializer((envelope) => {
if (envelope.tags) {
envelope.tags['ai.cloud.role'] = 'ui'
}
})
appInsights.loadAppInsights()

**Expected behavior**

applicationinsights-web implemented via npm will not load javascript from an external site

**Additional context**
We have a very strict CSP that blocks loading of scripts from external sites.
This cause a production showstopper for us since it was not listed as a breaking change that external scripts would now be loaded

Start with the npm initialization shown in the issue and compare the 3.1.2 and 3.2.0 browser behavior in Chrome. Trace the request to js.monitor.azure.com and verify that the npm-based SDK no longer attempts to load external JavaScript, while preserving the documented initialization path.

Written by the indexing model from the issue text.