Mac CI artifacts should link to provided libraries using @rpath or relative paths, not fixed paths in /usr/local/

[fredemmott]

For example:

fredemmott@fredemmott-fbmbp bin % otool -L thrift1
thrift1:
	/usr/local/lib/libssl.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
	/usr/local/lib/libcrypto.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 902.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1)

Those libraries in /usr/local/lib are not present, and can not be safely installed without interfering with system software (so homebrew refuses to use them)

Fortunately, they're included in the lib directory of this artifact, but they have the same problem:

fredemmott@fredemmott-fbmbp lib % otool -L libssl.1.1.dylib
libssl.1.1.dylib:
	libssl.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
	/usr/local/lib/libcrypto.1.1.dylib (compatibility version 1.1.0, current version 1.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1281.100.1)

Ideally CMake would link these with relative or rpath, but install_name_tool can be used to fix these up after the fact