fix(testing): force node10 module resolution for jest atomized tasks (#29421)

<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #

Author: leosvelperez

packages/jest/src/plugins/plugin.spec.ts

@@ -246,6 +246,9 @@ describe('@nx/jest/plugin', () => {
                     },
                     "options": {
                       "cwd": "proj",
+                      "env": {
+                        "TS_NODE_COMPILER_OPTIONS": "{"moduleResolution":"node10"}",
+                      },
                     },
                     "outputs": [
                       "{workspaceRoot}/coverage",

packages/jest/src/plugins/plugin.ts

@@ -407,6 +407,9 @@ async function buildJestTargets(
             outputs,
             options: {
               cwd: projectRoot,
+              env: {
+                TS_NODE_COMPILER_OPTIONS: '{"moduleResolution":"node10"}',
+              },
             },
             metadata: {
               technologies: ['jest'],