[foozzie] Also treat SIGABRT as crash

As with other crashes, also SIGABRT cuts of execution earlier. While
the reason might be interesting in normal fuzzing, in correctness
fuzzing, it leads to spurious reports due to the output differences.

No-Try: true
Bug: chromium:1242193
Change-Id: I6ee9a8e2a0254255d02b0106575931b523fbf666
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3124808
Auto-Submit: Michael Achenbach <machenbach@chromium.org>
Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
Cr-Commit-Position: refs/heads/main@{#76569}

tools/clusterfuzz/v8_commands.py

@@ -110,8 +110,7 @@ class Output(object):
     self.pid = pid
 
   def HasCrashed(self):
-    return (self.exit_code < 0 and
-            self.exit_code != -signal.SIGABRT)
+    return self.exit_code < 0
 
 
 def Execute(args, cwd, timeout=None):