Server Kaldi STT connection closing is buggy

[kdavis-mozilla]

A Kaldi STT connection to the server can be closed by the client or the server.

The current implementation handles the case in which the client closes the
connection correctly, but not the case in which the server closes it.

The code should be changed to handle both cases.

[kdavis-mozilla]

I have a fix[1], as much as is possible, in code local to to this repo.

However, there is a bug in the repo Java-WebSocket that we indirectly depend on that also must be fixed.

In particular, when a WebSocketClient is closed[2] what it first does is close it's socket[3], then notify the listeners[4][5] the socket is closed.

However, in the time between closing the socket and notifying the listeners any WebSocketClient subclass is unaware the socket is closed and thus continues to send data. It does so on a closed socket which leads to an exception.

The solution is to reverse the order in the method onWebsocketClose() and call onClose() before calling socket.close()