Timeout for stuck websocket connections

[pcapriotti]

This PR adds some cleanup logic for rabbitmq websocket connections that have been inactive for some configurable amount of time.

https://wearezeta.atlassian.net/browse/WPB-17895

Checklist

• Add a new entry in an appropriate subdirectory of changelog.d
• Read and follow the PR guidelines

[akshaymankar]

Have you seen the function withPingPong from websockets? Perhaps we don't have to implement this.

[akshaymankar]

Pending TODOs. Perhaps these value should come from configs and maybe we can write a test then?

[pcapriotti]

Something went wrong when I last rebased, it seems some commits got lost.

[pcapriotti]

Have you seen the function withPingPong from websockets? Perhaps we don't have to implement this.

I've seen it, but I can't see how to use it to implement our desired behaviour (i.e. only submit pings after inactivity).

[akshaymankar]

I've seen it, but I can't see how to use it to implement our desired behaviour (i.e. only submit pings after inactivity).

Hmm, perhaps its ok to just send pings all the time? The point of all this is to kill connections which have inactive clients.

[pcapriotti]

Sorry about the broken PR. Should be ok to review now.