chore: Update OpenSSL in CMake approach

[paleolimbot]

After #53, duckdb-geography fails to configure for me because it didn't like modifying the s2 target. I am wondering if this approach would also work (i.e., modify the s2geography target instead of the s2geometry target).

[paleolimbot]

@benbovy Any thoughts about this? I can more directly fix the error that I'm getting when building this in duckdb-geography, but this seems like a better approach than modifying the s2 target (unless it doesn't work!)

[benbovy]

This seems to work well too for building Spherely Python wheels:

benbovy/spherely#91
https://github.com/benbovy/spherely/actions/runs/12272251514?pr=91

Openssl is already a host explicit dependency in s2geography's conda-forge recipe so I don't see any issue with this approach, which seems better indeed.

[paleolimbot]

Thank you for giving this a shot! I have a feeling we're not done here (are we ever with CMake?), but hopefully this won't cause you problems.