Bump xharness to fix TCP issue in maccatalyst

[premun]

We started seeing a high number of APP_CRASH results caused by TCP problems so reverting the latest change in XHarness.

The problem means the OSX queues get clogged with work so we need to rush this in to unblock them. That's why this update is being done in isolation and will conflict with #82600

[ghost]

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

Issue Details

---

We started seeing a high number of APP_CRASH results caused by TCP problems so reverting the latest change in XHarness

Author:	premun
Assignees:	premun
Labels:	area-Infrastructure-libraries
Milestone:	-

[premun]

@steveisok could I ask you to watch over this and merge?

[ghost]

Tagging subscribers to 'os-maccatalyst': @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

Issue Details

---

We started seeing a high number of APP_CRASH results caused by TCP problems so reverting the latest change in XHarness.

The problem means the OSX queues get clogged with work so we need to rush this in to unblock them. That's why this update is being done in isolation and will conflict with #82600

Author:	premun
Assignees:	premun
Labels:	area-Infrastructure-libraries, os-maccatalyst
Milestone:	-

[akoeplinger]

@premun it was using 8d789cbeecb6c89bf470fdc7727a8f501724fc8a before which was before your change so this can't be related I think.

The xharness bump was still pending in #82600.

[premun]

@akoeplinger then we need to look in runtime for a regression. There was a considerable amount of maccatalyst crashes coming from all kinds of PRs since March 1st. The retries are clogging the 12.00 queue then.