trex server v2.88 ZMQ API interface changes

[hhaim]

Due to this issue, #636 there was a need to change the major API version to 5.0 (STL)

I will add the commit once it will be ready.

The high level changes from client side are:

1. Client should keep the ZMQ SUB/PUB but there is no need to read from it the information. The events shoudl be read using REQ/RES channel
2. Client must use a thread that pool the events using a new API get_async_events with session_id as an input. Each session will have a seperate queue for events. session_id is a unique number per session
3. Python client pool every 200msec the events queue
4. There is a new field in each event json called seq from type ```uint32``. Client could check that there is no missing events using this counter.

[leomaatEric]

Does it impact the ASTF mode implementation?

[hhaim]

@leomaatEric yes, in case of ASTF there is one more thing,
acquire command require session_id as in STL