Overload re2 cmakelists to fix cmake/threads detection issue on conda-forge mac builds, and pin C++ dependency versions

[timkpaine]

No description provided.

[texodus]

Is this a fix for the CI failure in #1632?

[timkpaine]

Tangentially related, i think re2's Cmakelists is incompatible with certain versions of mac os SDK (leading to the failures we see over on conda) so this applies the threading fix into it directly. #1632 would let you rely on a preinstalled version of re2 (and/or exprtk, and i'll have it do rapidjson and all our others) which will let us abide more by the rules of ecosystems like conda (and by extension, athena) by optionally not vendoring our dependencies at build time (but by still allowing that to keep our lives sane for our nice static builds for JS).

[timkpaine]

jesus azure get your shit together 😂 https://dev.azure.com/finosfoundation/perspective/_build/results?buildId=3646&view=logs&jobId=bfe8a88d-3928-550a-8c7c-c7cdeca2abfc&j=bfe8a88d-3928-550a-8c7c-c7cdeca2abfc&t=c266a550-8549-5644-3981-50c8d3f099c5

[timkpaine]

had to blow away yarn cache, full build in: https://dev.azure.com/finosfoundation/perspective/_build/results?buildId=3647&view=results

[timkpaine]

@texodus i think windows yarn cache is broken, did you run into this before? on another branch i turned it off, if thats acceptable i can do it here

[texodus]

Yes I have encountered this before and Azure has less-than-helpful advice for resolving it (e.g. rename the cache ona new branch). I am skeptical that perspective w/esbuild even benefits from this in terms of build time, so if its a blocker I think it is safe to remove.

[texodus]

Thanks for the PR! Looks good!

I am going to remove yarn caching entirely from our Azure script.