fix: Handle client disconnection for HTTP and WebSocket according to ASGI spec

For HTTP connections:
- If the app is sending data using the send callable, according to the ASGI spec, it should throw an exception
  in case of client disconnection. Previously, even if we processed the client_error message
  and set the http->closed state, it wouldn't throw an error because it wasn't handled.
  This change ensures that the exception is raised as per the ASGI spec.

For WebSocket connections:
- If the app is awaiting on receive, it would get a 'websocket.disconnect' event.
  However, if the app continues to send data using the send callable after receiving this event,
  it wouldn't raise an error because ws->state = NXT_WS_DISCONNECTED was never set in that case.
  According to the ASGI spec, if send is called after receiving a 'websocket.disconnect' event or on a closed client,
  it should raise an exception. This change ensures that the exception is raised as per the ASGI spec.

Author: gourav-kandoria

Diff for: src/python/nxt_python_asgi_http.c

@@ -367,6 +367,11 @@ nxt_py_asgi_http_response_body(nxt_py_asgi_http_t *http, PyObject *dict)
                             "Unexpected ASGI message 'http.response.body' "
                             "sent, after response already completed");
     }
+    
+    if (nxt_slow_path(http->closed)) {
+        return PyErr_Format(PyExc_RuntimeError,
+                            "Connection Closed ");
+    }
 
     if (nxt_slow_path(http->send_future != NULL)) {
         return PyErr_Format(PyExc_RuntimeError, "Concurrent send");

Diff for: src/python/nxt_python_asgi_websocket.c

@@ -984,9 +984,9 @@ nxt_py_asgi_websocket_close_handler(nxt_unit_request_info_t *req)
         return;
     }
 
-    if (ws->receive_future == NULL) {
-        ws->state = NXT_WS_DISCONNECTED;
+    ws->state = NXT_WS_DISCONNECTED;
 
+    if (ws->receive_future == NULL) {
         return;
     }