Fix requireActual fail with moduleNameMapper

[levinqdl]

Summary

This PR fixes #7981 , requireActual not work with moduleNameMapper, witch currently throws an error.

This PR make jest-resolve resolveModule invoke resolveStubModuleName, which resolves module with moduleNameMapper. resolveStubModuleName is invoked before resolveModuleFromDirIfExists, so that moduleNameMapper config can override default behavior.

Test plan

Test requireActual with a moduleNameMapper configuration, and it should resolve the module successfully.

[codecov-io]

Codecov Report

Merging #8210 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8210      +/-   ##
==========================================
+ Coverage   62.29%   62.34%   +0.04%     
==========================================
  Files         265      265              
  Lines       10551    10551              
  Branches     2563     2564       +1     
==========================================
+ Hits         6573     6578       +5     
+ Misses       3388     3385       -3     
+ Partials      590      588       -2

Impacted Files	Coverage Δ
packages/jest-resolve/src/index.ts	44.11% <100%> (+3.67%)	⬆️

---

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 4b3483e...8bcdffb. Read the comment docs.

[SimenB]

Thanks for the PR! I think this makes sense :)

[thymikee]

Looks good! It also doesn't seem to cause measurable performance impact (cold & warm cache) for a non-mapped test suite as we have in src/packages/*.

Would like @scotthovestadt to also have a look

@levinqdl mind resolving the conflicts?

[levinqdl]

Hi @thymikee, conflicts have been resolved.

[thymikee]

Ok, merging. Thanks you so much @levinqdl! Looking forward to future contributions :)

[frontendphil]

This just broke quite a lot of our tests, so I came here to complain but then realized that we relied on a buggy implementation and that I misread the docs. Fixed our setup and needed to leave this comment.

[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.