PT47192769 - Make SQA HA
PT47290759 - Add config side support for SQA HA
PT50071971 - redis-client.ini is not replicated on HA nodes

Initial commit for SQA HA with changes in SQA core and config side support:
- sqa client interface was rewritten to allow one client to use multiple sqa agents;
- a sqa client publisher or dealer will connect to one agent only;
- a sqa client watcher or worker will connect to all available agents;
- one sqa client publisher or dealer can do fallback through several agents in case some agents fail;
- watcher or worker sqa clients cannot do fallback;
- sqa client keepalive and signin procedures were simplified;
- config side support for SQA HA was added: SQA agent can be started on any node; Redis server can be started on only one node;
- some code was refactored to ease implementation of HA support or removed duplicates (i.e code dealing with generating event ids);

Other fixes and changes were done in SQA:
- add support for new client methods to pop & watch with timeout;
- removed the unused mongo oplog code from StateQueueAgent;
- couple of bugfixes in redis client code: redis hset/hget command was not constructed properly and could not be used, interpretation of status response from redis was wrong,
  disconnect callback was not set ok,
- added a new container for work events SQAEventEx, the existing SQAEvent will continue to be used for watched events;
- sqa client is now compiled as a standalone library and is not header-only anymore; all components using SQA clients were updated to use the new library;

Unit tests were done for StateQueueClient, SQAClientCore, StateQueueAgent, lots of helper utilities;
UC-1185 Investigate log entry "received response without transaction"

Lowered the log level from WARNING to INFO. This message is logged for
every response passing the UA for which a live transaction could not be found.
We chose to keep it on INFO level and not lower it to  DEBUG level
because this log is a way of measuring the proxy's effort of forwarding
responses with no transaction. However on some scenarios it should be expected
because proxy's NatMaintainer does keep alive by sending an OPTION request with
no transaction, so, for every OPTION message send by NatMaintainer this
log message will be logged.
UC-1472 Proxy should forward statelessly multiple 2xx responses to INVITE requests

The stacklib's UserAgent class was updated to send statelessly any 200 OK
responses to INVITE requests. Any other responses will just be ignored.
XX-10758 Proxy high cpu utilization when disabling Bria's TLS account

Sometimes, when reading EOF from socket, proxy was entering in a loop
sending empty keep-alives messages to itself. To fix this proxy should
check for keep alives only if EOF was not read.
Merge branch 'XX-10758' into release-4.6
Merge branch 'UC-1472' into release-4.6
Merge remote-tracking branch 'origin/SSS-main' into SSS-main
Merge remote-tracking branch 'origin/sqa-ha' into SSS-main
Merge remote-tracking branch 'origin/SSS-main' into SSS-main