docs(testing): fix docs on how to debug jest tests

Author: vsavkin

docs/shared/jest-plugin.md

@@ -104,7 +104,7 @@ nx test libname --watch
 To debug failing tests using Chrome Devtools or an IDE you can run the test command through node's `--inspect-brk` flag.
 
 ```bash
-node --inspect-brk ./node_modules/nx/bin/nx test libname
+node --inspect-brk ./node_modules/@nrwl/cli/bin/nx test libname
 ```
 
 Now, you can visit [chrome://inspect](chrome://inspect) in Chrome and inspect the target to attach to the node process. You can now use Chrome Devtools to step through your code line by line and debug the cause of the failing tests. Visit the official [Jest documentation](https://jestjs.io/docs/en/troubleshooting#tests-are-failing-and-you-don-t-know-why) to find out more.

nx-dev/archive/10.4.13/shared/jest-plugin.md

@@ -104,7 +104,7 @@ nx test libname --watch
 To debug failing tests using Chrome Devtools or an IDE you can run the test command through node's `--inspect-brk` flag.
 
 ```bash
-node --inspect-brk ./node_modules/nx/bin/nx test libname
+node --inspect-brk ./node_modules/@nrwl/cli/bin/nx test libname
 ```
 
 Now, you can visit [chrome://inspect](chrome://inspect) in Chrome and inspect the target to attach to the node process. You can now use Chrome Devtools to step through your code line by line and debug the cause of the failing tests. Visit the official [Jest documentation](https://jestjs.io/docs/en/troubleshooting#tests-are-failing-and-you-don-t-know-why) to find out more.

nx-dev/archive/10.4.13/shared/tools-workspace-schematics.md

@@ -296,7 +296,7 @@ Alternatively press <kbd>Cmd</kbd>+<kbd>P</kbd> (or <kbd>Ctrl</kbd>+<kbd>P</kbd>
 Once you've activated the `autoAttach` option, set a breakpoint in VSCode and execute your schematic with the `--inspect-brk` flag:
 
 ```sh
-node --inspect-brk ./node_modules/nx/bin/nx.js workspace-schematic my-schematic mylib --dry-run
+node --inspect-brk ./node_modules/@nrwl/cli/bin/nx.js workspace-schematic my-schematic mylib --dry-run
 ```
 
 You may want to use the `--dry-run` flag to not actually apply the changes to the file system.

nx-dev/archive/11.4.0/shared/jest-plugin.md

@@ -104,7 +104,7 @@ nx test libname --watch
 To debug failing tests using Chrome Devtools or an IDE you can run the test command through node's `--inspect-brk` flag.
 
 ```bash
-node --inspect-brk ./node_modules/nx/bin/nx test libname
+node --inspect-brk ./node_modules/@nrwl/cli/bin/nx test libname
 ```
 
 Now, you can visit [chrome://inspect](chrome://inspect) in Chrome and inspect the target to attach to the node process. You can now use Chrome Devtools to step through your code line by line and debug the cause of the failing tests. Visit the official [Jest documentation](https://jestjs.io/docs/en/troubleshooting#tests-are-failing-and-you-don-t-know-why) to find out more.