errors lead to consistent exit code in issue detail (vercel/turborepo…

…#4716)

### Description

issue snapshots are flaky due to alternating issue detail with exist
code or not.

It's a race condition between process exit after sending error and
process killing after receiving error.

crates/turbopack-node/js/src/ipc/index.ts

@@ -134,8 +134,9 @@ function createIpc<TIncoming, TOutgoing>(
         });
       } catch (err) {
         // ignore and exit anyway
+        process.exit(1);
       }
-      process.exit(1);
+      process.exit(0);
     },
   };
 }

crates/turbopack-node/src/render/issue.rs

@@ -38,7 +38,9 @@ impl Issue for RenderingIssue {
         let mut details = vec![];
 
         if let Some(status) = self.status {
-            details.push(format!("Node.js exit code: {status}"));
+            if status != 0 {
+                details.push(format!("Node.js exit code: {status}"));
+            }
         }
 
         Ok(StringVc::cell(details.join("\n")))