feat(testing): add --force-exit to jest executor (#17790)

docs/generated/packages/jest/executors/jest.json

@@ -81,6 +81,10 @@
         "description": "Find and run the tests that cover a comma separated list of source files that were passed in as arguments. (https://jestjs.io/docs/cli#--findrelatedtests-spaceseparatedlistofsourcefiles)",
         "type": "string"
       },
+      "forceExit": {
+        "description": "Force Jest to exit after all tests have completed running. This is useful when resources set up by test code cannot be adequately cleaned up.This feature is an escape-hatch. If Jest doesn't exit at the end of a test run, it means external resources are still being held on to or timers are still pending in your code. It is advised to tear down external resources after each test to make sure Jest can shut down cleanly. You can use --detectOpenHandles to help track it down.",
+        "type": "boolean"
+      },
       "json": {
         "description": "Prints the test results in `JSON`. This mode will send all other test output and user messages to `stderr`. (https://jestjs.io/docs/cli#--json)",
         "type": "boolean"

packages/jest/src/executors/jest/jest.impl.ts

@@ -71,6 +71,7 @@ export async function jestConfigParser(
     ci: options.ci,
     color: options.color,
     detectOpenHandles: options.detectOpenHandles,
+    forceExit: options.forceExit,
     logHeapUsage: options.logHeapUsage,
     detectLeaks: options.detectLeaks,
     json: options.json,

packages/jest/src/executors/jest/schema.d.ts

@@ -15,6 +15,7 @@ export interface JestExecutorOptions {
   color?: boolean;
   clearCache?: boolean;
   findRelatedTests?: string;
+  forceExit?: boolean;
   json?: boolean;
   maxWorkers?: number | string;
   onlyChanged?: boolean;

packages/jest/src/executors/jest/schema.json

@@ -90,6 +90,10 @@
       "description": "Find and run the tests that cover a comma separated list of source files that were passed in as arguments. (https://jestjs.io/docs/cli#--findrelatedtests-spaceseparatedlistofsourcefiles)",
       "type": "string"
     },
+    "forceExit": {
+      "description": "Force Jest to exit after all tests have completed running. This is useful when resources set up by test code cannot be adequately cleaned up.This feature is an escape-hatch. If Jest doesn't exit at the end of a test run, it means external resources are still being held on to or timers are still pending in your code. It is advised to tear down external resources after each test to make sure Jest can shut down cleanly. You can use --detectOpenHandles to help track it down.",
+      "type": "boolean"
+    },
     "json": {
       "description": "Prints the test results in `JSON`. This mode will send all other test output and user messages to `stderr`. (https://jestjs.io/docs/cli#--json)",
       "type": "boolean"