#1774 change hwm limits for zmq broadcast

[olehnikolaiev]

fixes #1774

Description

Set ZMQ sockets hard limits to 0 to avoid messages being dropped out from the buffer.

Tests

Tested on the network with historic node and 7 core nodes:

run load test and send all transactions to the historic node
wait for some time (30 min is enough)
stop the load
there will be transactions in transaction queue on the historic node (version 3.18) that stuck there. Wait for 5 more minutes and ensure that those transactions will still be there. it means that these transactions were marked as broadcasted but were dropped out of the socket's buffer and therefore weren't received by other nodes.
there will be no stuck transactions on the historic node built on this branch

Performance Impact

Tested on the network with historic node and 7 core nodes:

run load test for ~2 hours on both new and current versions
ram usage on the new version will not be higher than ram usage on the current version (current version - 500 mb usage, new version - 350-400 mb)
Tested on the devnet - 4-node chain

run load test for 24 hours
ram usage is normal, no swap growth

results verified by @oleksandrSydorenkoJ

[github-actions]

SUGGESTIONS BEFORE MERGE:

1. Build custom container here: https://github.com/skalenetwork/skaled/actions?query=workflow%3A%22Custom+Docker+and+Binary%22
2. Test it here: https://github.com/skalenetwork/skale-ci-integration_tests/actions?query=workflow%3A%22Skaled+Nightly+Tests%22
3. Edit VERSION file appropriately to your changes!
   See https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/2444951553/Branching+instructions