Constant disconnects in dotnet-unified-build pipeline

[ViktorHofer]

Example: https://dnceng.visualstudio.com/internal/_build/results?buildId=2437451&view=logs&j=5551d7c4-237a-5520-de91-e8efe1228738

We are experiencing disconnects when using the macos-13-arm64 pool on nearly every queued build and with the following message:

##[error]We stopped hearing from agent Azure Pipelines 23. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610

In an effort to get the VMR unified build pipeline green and then enable pipeline notifications, we are considering switching back to the macos-12 pool. That pool unfortunately is still plagued with the slow macOS issue.

Some guidance and links to the IcM tickets that track resolving these issues would be appreciated.

cc @ilyas1974 @mmitche

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ilyas1974]

I reached out to my contacts on the team that manages this pool to get current information about some of the changes they had planned for this pool.

[ViktorHofer]

@ilyas1974 kindly asking for an update in case you already heard back.

[ilyas1974]

Let me follow up - last I heard they were going to look at the backend telemetry to see what is going on.