test: unflake test-vm-timeout-escape-nexttick

This wasn't failing on arm boxes, increase the `runInNewContext()`
timeout a bit to make sure the code it's allowed to fail.

PR-URL: nodejs#48078
Fixes: nodejs#43931
Fixes: nodejs#42496
Fixes: nodejs#47715
Fixes: nodejs#47259
Fixes: nodejs#47241
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
Reviewed-By: Debadree Chatterjee <debadree333@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>

test/known_issues/test-vm-timeout-escape-nexttick.js

@@ -13,7 +13,7 @@ const NS_PER_MS = 1000000n;
 const hrtime = process.hrtime.bigint;
 const nextTick = process.nextTick;
 
-const waitDuration = common.platformTimeout(100n);
+const waitDuration = common.platformTimeout(200n);
 
 function loop() {
   const start = hrtime();
@@ -38,7 +38,7 @@ for (let i = 0; i < 4; i++) {
         nextTick,
         loop,
       },
-      { timeout: common.platformTimeout(10) },
+      { timeout: common.platformTimeout(100) },
     );
   }, {
     code: 'ERR_SCRIPT_EXECUTION_TIMEOUT',