perf(haste-map): default to node crawl if watchman is not enabled

[SimenB]

Summary

Toggling option from #11264.

On my machine the node crawl is even faster than watchman for --list-tests, while both beat find into dust.

This branch:

$  hyperfine 'yarn jest --list-tests' 'yarn jest --list-tests --no-watchman'
Benchmark 1: yarn jest --list-tests
  Time (mean ± σ):      2.921 s ±  0.750 s    [User: 3.143 s, System: 0.549 s]
  Range (min … max):    2.261 s …  4.519 s    10 runs

Benchmark 2: yarn jest --list-tests --no-watchman
  Time (mean ± σ):      2.197 s ±  0.216 s    [User: 2.367 s, System: 0.414 s]
  Range (min … max):    2.074 s …  2.801 s    10 runs

main:

$ hyperfine 'yarn jest --list-tests --no-watchman'
Benchmark 1: yarn jest --list-tests --no-watchman
  Time (mean ± σ):      3.684 s ±  0.364 s    [User: 2.878 s, System: 1.415 s]
  Range (min … max):    3.225 s …  4.341 s    10 runs

Test plan

Green CI

[codecov-commenter]

Codecov Report

Merging #12320 (1a2ebd5) into main (762b9b7) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #12320      +/-   ##
==========================================
- Coverage   67.25%   67.25%   -0.01%     
==========================================
  Files         330      330              
  Lines       17354    17354              
  Branches     5073     5073              
==========================================
- Hits        11672    11671       -1     
- Misses       5650     5651       +1     
  Partials       32       32              

Impacted Files	Coverage Δ
packages/jest-config/src/Defaults.ts	100.00% <ø> (ø)
packages/jest-config/src/ValidConfig.ts	100.00% <ø> (ø)
packages/expect/src/utils.ts	96.09% <0.00%> (-0.49%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 762b9b7...1a2ebd5. Read the comment docs.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.