[MIE-1492] Too many Redis Connections

## Activity Streams creates too many Redis Connections.

Redis service dissconnects clients those who stand for 5 minutes in idle state. Then once the client detect that connection is gon, it tries to recconect and creates a new connection.

#### Changelog

- A new module redisWrapper was added in order to create a section where we could overwrite functionality from redis adpater.

- For each 4 minutes on idle state, the client will send a command queue (for instance "select(1)") what resets the idle timmer at redis service.
Good point.

My goal is to send keep alive after 4' idle. To achieve that, we use a timeOut, if this timeOut already exits (means that the previous keep alive was not sent yet) then clears the last timeOut and resets the timer. By doing this we are sending the minimum amount keep alives as possible.

Regarding to 'idle' event, this is fired whenever a job has finished and there are no more task in queue. So if we just send keep alive, this job ends quickly and then a new idle callback is fired. That becomes too many keep alives.

Perhaps timmerKeepAlive makes confuse for you, (have you thought for setInterval?), i am thinking to change this into "sendNextAlive(...)"