[BUG] disableCorrelationHeaders does not work as expected

Nobody has claimed this yet.

**Description/Screenshot**

[Documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/app/javascript-sdk-configuration) for `disableCorrelationHeaders` attribute says

> If false, the SDK adds two headers ('Request-Id' and 'Request-Context') to all dependency requests to correlate them with corresponding requests on the server side. Default is false.

But the mentioned header `Request-Id` is sent only if attribute `enableCorsCorrelation` is set to true and `Request-Context` is sent only if `enableCorsCorrelation` is set to true and `appId` is not undefined.

**Steps to Reproduce**

- OS/Browser: win 11, edge
- SDK Version [e.g. 22]: `"@microsoft/applicationinsights-clickanalytics-js": "^3.2.1"`
- How you initialized the SDK: npm

**Expected behavior**

I expect that `Request-Id` and `Request-Context` will be sent when `disableCorrelationHeaders` is false.

Start with the configuration documentation linked in the issue, then search the TypeScript source and tests for disableCorrelationHeaders, enableCorsCorrelation, Request-Id, and Request-Context. Reproduce the dependency-request behavior and trace the conditions controlling each header; the issue is done when the intended behavior is implemented or documented and covered by regression tests.

Written by the indexing model from the issue text.