[Identity] node-fetch takes above 2 seconds to send the request on some environments

[sadasant]

While we stopped using node-fetch on core-rest-pipeline, core-http does use it. Node fetch takes above 2 seconds to begin sending network requests in some environments. We’re able to reproduce this issue in Kubernetes pods, but it could be present elsewhere.

This PR increases the timeout to 3 seconds.

I believe this should be ok as a temporary solution, since in many cases, we will get a response (any response) before that time.

For Identity. we should be able to solve this as soon as we move Identity to core-rest-pipeline: #15595 We’re planning to do this during July. However, that won’t solve the issue in core-http.

This issue is related to: #15935

It won’t fix #15935, but it will help us have an immediate aid for our customers.

[xirzec]

I'm not opposed to this change, though can you file a tracking bug to remove this as part of the switch to corev2?

[sadasant]

@xirzec yes yes, I’ll move this back as part of moving Identity to core-rest-pipeline: #15595