fix(node): Avoid catching domain errors in request handler (#5627)

According to the Node.js docs, domain errors are equivalent to an uncaught exception and therefore should not really be caught except to do some cleanup and then exit the process. Not doing so causes the process to potentially linger without being able to handle any request. Currently, the behaviour is also erroneous because `next` can end up be called twice.

Author: mohd-akram

packages/node/src/handlers.ts

@@ -153,7 +153,6 @@ export function requestHandler(
     const local = domain.create();
     local.add(req);
     local.add(res);
-    local.on('error', next);
 
     local.run(() => {
       const currentHub = getCurrentHub();