Petevdp/resolve mock dependencies

[petevdp]

Summary

fixes #8907

DependencyResolver.resolve resolves the functional dependencies for a given file, but it doesn't include potential mock dependencies. This means that, as the issue lays out, updates to mocks won't register as an affecting change for tests.

The changes I made will include mocks with names matching any functional dependency during the resolution process. Note this won't take into account any in-code dependency declarations, but it solves the problem in an unobtrusive way.

Test plan

I added a unit test describing this new requirement, and it passes along with all previously passing tests. There are some failing tests when running the full test suite, but they appear to be pre-existing.

Here's the output of running the dependency resolver tests:

 PASS  packages/jest-resolve-dependencies/src/__tests__/dependency_resolver.test.ts
  ✓ resolves no dependencies for non-existent path (255ms)
  ✓ resolves dependencies for existing path (13ms)
  ✓ includes the mocks of dependencies as dependencies (8ms)
  ✓ resolves dependencies for scoped packages (7ms)
  ✓ resolves no inverse dependencies for empty paths set (8ms)
  ✓ resolves no inverse dependencies for set of non-existent paths (9ms)
  ✓ resolves inverse dependencies for existing path (9ms)
  ✓ resolves inverse dependencies from available snapshot (10ms)

Test Suites: 1 passed, 1 total
Tests:       8 passed, 8 total
Snapshots:   0 total
Time:        0.791s, estimated 1s
Ran all test suites matching /\/home\/pete\/Code\/contributions\/jest\/jest\/packages\/jest-resolve-dependencies\/src\/__tests__\/dependency_resolver.test.ts/i.

A test of the scenario given in the referenced issue also fixes the problem.

This is my first pull request, so apologies in advance for any miss-steps. I'll do my best to correct them quickly!

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