Consider using zstd instead of zlib

### Is your feature request related to a problem?

Data storage is essential to be as small as possible to increase storage capacity of node and scalability

### Describe the solution you'd like

We currently use zlib for the compression of some data.
We could consider using zstd instead which provide a better compression ratio and a faster compression / decompression speed.
There is a maintained package in erlang https://hexdocs.pm/ezstd/ezstd.html

### Additional context

_No response_

### Epic

_No response_

Start by locating the existing zlib compression and decompression paths in the node, then read the linked ezstd package documentation. Assess which stored data and compatibility constraints would be affected by switching to zstd. Done means the migration scope, compatibility requirements, and expected storage and speed impact are established.

Written by the indexing model from the issue text.