Handle WebSockets disconnection

[imobachgs]

Problem

Agama does not handle WebSockets disconnections properly. When a client gets disconnected, Agama insists on sending the events to the client.

Solution

Properly handle WebSockets disconnection. In the example below, you can read the logs in that case (they are coming from tungstenite):

dic 18 22:22:51 agama agama-web-server[6893]: Received close frame: Some(CloseFrame { code: Away
, reason: "" })
dic 18 22:22:51 agama agama-web-server[6893]: Replying to close with Frame { header: FrameHeader
 { is_final: true, rsv1: false, rsv2: false, rsv3: false, opcode: Control(Close), mask: None }, 
payload: [3, 233] }

Additionally, Agama does not send the events from the old API anymore.

Testing

• Tested manually

[jreidinger]

Maybe this deserve a comment as I need to check exact websocket API to understand all cases (explicit close message, None for closed stream and error for generic axum error ). And I am not sure if breaking in case of generic axum error is good or not as sadly reading axum code for method recv does not help understand when it can return Err

[jreidinger]

much better than before