Fix large log files (>70Mb) causing rageshake servers to return 403

[MidhunSureshR]

• Use a dependency to compress the logs before upload. Generally we don't prefer adding dependencies for things like this.
• Make logging the membership changes optional with a config.
• Switch over to using open telemetry (but this would not fix the issue)
• Check if we really need to log all this data (eg: do we need to log all the membership changes? What exactly is a 'membership change'?)

[MidhunSureshR]

Hydrogen will load non terminated calls at startup. Each membership event associated with a call is logged. If a call has a large number of membership events associated with it (say 600), Hydrogen will add 600 log items each time it starts. This is what is inflating the log file.

[MidhunSureshR]

The easy fix is to not log expired members which form the bulk of the logs.