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;