fix(node-core): do not print rejection warning in strict mode

This matches the behavior of Node.js.

Author: mohd-akram

dev-packages/node-core-integration-tests/suites/public-api/onUnhandledRejectionIntegration/test.ts

@@ -52,8 +52,7 @@ Error: test rejection
         expect(err?.code).toBe(1);
         expect(stdout).not.toBe("I'm alive!");
         expect(stderr)
-          .toContain(`This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
-test rejection`);
+          .toBe('');
         done();
       });
     }));

packages/node-core/src/integrations/onunhandledrejection.ts

@@ -143,9 +143,6 @@ function handleRejection(reason: unknown, mode: UnhandledRejectionMode): void {
       console.error(reason && typeof reason === 'object' && 'stack' in reason ? reason.stack : reason);
     });
   } else if (mode === 'strict') {
-    consoleSandbox(() => {
-      console.warn(rejectionWarning);
-    });
     logAndExitProcess(reason);
   }
   /* eslint-enable no-console */