cargo-c: use specified version of openssl

[ZhongRuoyu]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

In #125208 where rust is being switched to openssl@3, cargo-c reported No linkage with libssl.dylib! Cargo is likely using a vendored version. (log). It is likely using rust's openssl@3 dependency, instead of the declared openssl@1.1.

[ZhongRuoyu]

To make sure, I will rebase this and mark it as "Ready for review" after #125208 is merged.

[Porkepix]

To make sure, I will rebase this and mark it as "Ready for review" after #125208 is merged.

Can't it be switched to openssl 3 after rust switch is merged?

[ZhongRuoyu]

Can't it be switched to openssl 3 after rust switch is merged?

Not yet, because of libssh2. It links with openssl@1.1.

[ZhongRuoyu]

Actually, since #124227 revbumps cargo-c, this PR should wait for that too.