Cross-Origin-Embedder-Policy support

**Is your feature request related to a problem? Please describe.**
When trying to set the [Cross-Origin-Embedder-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy) header to "require-corp" on my site, requests to application insights (in particular https://australiaeast-0.in.applicationinsights.azure.com//v2/track) are blocked, as they do not have a [Cross-Origin-Resource-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy) header.

**Describe the solution you'd like**
The application insights endpoints to serve a Cross-Origin-Resource-Policy header of the value "cross-origin".

**Describe alternatives you've considered**
If this was an image or script request, I could add the crossOrigin attribute to the or tag to get around this problem. However, this is a fetch/XHR request, and one that requires cookies if I understand correctly.

**Additional context**
Cross-Origin-Embedder-Policy is needed to enable the security feature cross-site isolation.

Start by tracing how the SDK sends requests to the Application Insights endpoint, particularly the australiaeast-0.in.applicationinsights.azure.com/v2/track endpoint. Determine whether response headers are controlled in this repository or by the Application Insights service; done means the endpoint supplies Cross-Origin-Resource-Policy: cross-origin for these requests.

Written by the indexing model from the issue text.