HttpStress: Disable firewall in Windows runs

[antonfirsov]

Fixes #50854. The issue seems to be caused by an unknown firewall problem, and from the POV of http stress testing it's a false negative. We need a quick solution to remove this failure type, because the high amount failures renders our stress test reports useless.

Since the build agents do not have a public IP, it seems OK to disable the Windows firewall for the runs.

/cc @MattGal @ViktorHofer

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Fixes #50854. The issue seems to be caused by an unknown firewall problem. Since the build agents do not have a public IP, it seems OK to disable the Windows firewall for the runs.

/cc @MattGal @ViktorHofer

Author:	antonfirsov
Assignees:	-
Labels:	area-System.Net.Http
Milestone:	-

[antonfirsov]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[antonfirsov]

In the first run, failure happened in HTTP 2.0 (HTTP2 failure types known and documented in #42211):
https://dev.azure.com/dnceng/public/_build/results?buildId=1125329&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=abae1f68-3c73-5bff-491f-f2b908580ce6

[antonfirsov]

/azp run runtime-libraries stress-http

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[GrabYourPitchforks]

Disabling the firewall seems appropriate for this scenario. Is it possible to shrink the window any further than this PR proposes? For example, can the "disable firewall" rule be moved after the build but before the stress run? If the build also requires it for some reason, then no worries.

[wfurt]

I think we need to do that only for the stress run itself as it interferes with the load. Everything else is working OK AFAIK.

[antonfirsov]

@GrabYourPitchforks @wfurt limited the disable window to the HTTP 1.1 run, HTTP 2.0 is not impacted by #50854.

[GrabYourPitchforks]

Thanks!