Disable GetAsync_UnicodeHostName_SuccessStatusCodeInResponse

[alnikola]

SocketsHttpHandlerTest_HttpClientHandlerTest_Http2.GetAsync_UnicodeHostName_SuccessStatusCodeInResponse is periodically failing with TimeoutException. It seems to be caused by the target server unavailability, this PR disables the test until a new unicode test host is found.

[ghost]

Tagging subscribers to this area: @dotnet/ncl
Notify danmosemsft if you want to be subscribed.

[alnikola]

/azp run runtime-libraries outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephentoub]

this PR increases timeout to 200 sec.

Isn't this the test where we've found that the site is sometimes just down? I'm not sure increasing the timeout is going to help.

[stephentoub]

#29424

[davidsh]

I was under the impression that this test was already disabled as a result of #29424 issue. That's why it is marked 'disabled-test'. But apparently this test wasn't actually disabled.

So, I think this PR should be changed to simply disable this test. It's useless increasing the timeout.

[davidsh]

And the future plan for this test was discussed at a previous team meeting.

Summary:

As we discussed in the team meeting, we plan to move this test to either a unicode DNS server that we own (similar to our other Azure servers) or move this test to a different pipeline like the runtime-libraries enterprise-linux pipeline which has Linux docker images in its own network and can use custom DNS. I was going to work on this test later.