Fix LibSSL installation on osx.1200.arm64.open / osx.1200.amd64.open

[MattGal]

As reported in dotnet/runtime#79619 . I will investigate, fix up the machines, and follow up with DDFUN why these machines got into the state (seems to be all / many of the machines in these pools)

[MattGal]

Tagging @wfurt since this does not match previous symptoms. On every machine I've checked that has failed this work item recently, OpenSSL 1.1.1s was installed and linked into /usr/local/lib/libcrypto.1.1.dylib , which was the previous problem. I am continuing to investigate.

[MattGal]

I think I figured it out. On these machines, OpenSSL 1.1.1s is installed, while the link in /usr/local/lib points to a non-existent 1.1.1k version.

I will spend a few minutes to see if I can figure out how this occurred, then write some scripts to fix up the paths on these machines.

[MattGal]

This seems to be fallout from doing #11631, where we've learned any brew update could result in breaking this link, even when the packages being installed aren't openssl.

[MattGal]

I updated all the machines and ran just this work item cloned from an existing run to show that it works. Closing issue.

WorkItems
| where JobName == "5a8b870c-ef6a-47f3-ade7-9acbd9028445" // open test of openssl

WorkItems
| where JobName == "61ecd54d-a207-4a62-8b8a-5637e4e0df9f" // closed test of openssl