statically-link dependencies into tor daemon

We ship our own versions of libevent, openssl, etc with tor in Tor Browser. This can cause issues when systems do not use these packaged libraries ( like in tor-browser#41336 ).

We should statically link our dependencies into the tor daemon. This will ensure we are actually, using the implementation we think we are, and it should reduce the final package/install size as LTO will ensure we are only building and linking in the symbols actually used.

Ricochet-Refresh builds openssl, zlib and libevent this way for tor on Windows (x86,x64), Linux (x86,x64), and macOS (x64):

• openssl: https://github.com/blueprint-freespeech/ricochet-build/tree/main/projects/openssl
• libvent: https://github.com/blueprint-freespeech/ricochet-build/tree/main/projects/libevent
• zlib: https://github.com/blueprint-freespeech/ricochet-build/tree/main/projects/zlib
• tor: https://github.com/blueprint-freespeech/ricochet-build/tree/main/projects/tor

Android is not currently built/supported so anything in there referncing it is left-overs from the original tor-browser-build fork.