Close HTTP response on unhandled request timeout (#2007)

* Close HTTP response on unhandled request timeout

This commit updates the defaultUnhandledRequestHandler to close the HTTP
response when an incoming event is not acknowledged within the expected
timeframe. This change ensures that resources are not left hanging and
that the server correctly indicates to the client that the event was not
processed as expected.

By sending a 503 Service Unavailable status code and ending the response,
we provide clearer semantics and prevent potential resource leaks on the
server.

* Update error code as per code review feedback

Author: suhailgupta03

src/receivers/HTTPModuleFunctions.spec.ts

@@ -318,6 +318,7 @@ describe('HTTPModuleFunctions', async () => {
           request,
           response,
         });
+        assert.isTrue(writeHead.calledWith(404));
       });
     });
   });

src/receivers/HTTPModuleFunctions.ts

@@ -219,11 +219,18 @@ export class HTTPModuleFunctions {
   // Developers can customize this behavior by passing unhandledRequestHandler to the constructor
   // Note that this method cannot be an async function to align with the implementation using setTimeout
   public static defaultUnhandledRequestHandler(args: ReceiverUnhandledRequestHandlerArgs): void {
-    const { logger } = args;
+    const { logger, response } = args;
     logger.error(
       'An incoming event was not acknowledged within 3 seconds. ' +
       'Ensure that the ack() argument is called in a listener.',
     );
+
+    // Check if the response has already been sent
+    if (!response.headersSent) {
+      // If not, set the status code and end the response to close the connection
+      response.writeHead(404); // Not Found
+      response.end();
+    }
   }
 }