fix: Prevent process from hanging after tests complete

- Add force-exit timeout (100ms) in run command to ensure process exits
- Respects --no-exit flag if explicitly set
- Increase browser stop timeout from 5s to 10s for browser restart strategy

This fixes an issue where tests would complete successfully but the Node.js
process would hang indefinitely, waiting for the event loop to clear.
The issue was caused by Mocha 11.x waiting for all handles to close,
but some browser-related handles may remain open even after proper cleanup.

The force-exit gives cleanup operations time to complete (100ms) then
explicitly calls process.exit() to terminate the process cleanly.

Author: kobenguyent

lib/command/run.js

@@ -42,5 +42,14 @@ export default async function (test, options) {
     process.exitCode = 1
   } finally {
     await codecept.teardown()
+    
+    // Force exit if event loop doesn't clear naturally
+    // This is needed because some helpers (like Playwright) may leave handles open
+    // even after proper cleanup, preventing natural process termination
+    if (!options.noExit) {
+      setTimeout(() => {
+        process.exit(process.exitCode || 0)
+      }, 100)
+    }
   }
 }

lib/helper/Playwright.js

@@ -718,10 +718,10 @@ class Playwright extends Helper {
             const pages = await this.browserContext.pages()
             await Promise.allSettled(pages.map(p => p.close().catch(() => {})))
           }
-          // Use timeout to prevent hanging
+          // Use timeout to prevent hanging (10s should be enough for browser cleanup)
           await Promise.race([
             this._stopBrowser(),
-            new Promise((_, reject) => setTimeout(() => reject(new Error('Browser stop timeout')), 5000)),
+            new Promise((_, reject) => setTimeout(() => reject(new Error('Browser stop timeout')), 10000)),
           ])
         } catch (e) {
           console.warn('Warning during browser restart in _after:', e.message)