Executing globalConfig only when there are tests available to be exec…

[anilreddykatta]

…uted

Summary
Currently, we execute globalConfig module even when there are no tests available for execution. Fixes #5315

Test plan
Currently, we should not see "determining test suites to run" when there are no available tests.

[codecov-io]

Codecov Report

Merging #5323 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master    #5323   +/-   ##
=======================================
  Coverage   61.25%   61.25%           
=======================================
  Files         205      205           
  Lines        6896     6896           
  Branches        3        4    +1     
=======================================
  Hits         4224     4224           
  Misses       2671     2671           
  Partials        1        1

Impacted Files	Coverage Δ
packages/jest-cli/src/run_jest.js	52.54% <50%> (ø)	⬆️

---

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 dd848f3...142988b. Read the comment docs.

[cpojer]

Thanks! Could you make a second PR with an update to the changelog as well as an integration test? You could make it so that the globalSetup would call "console.log" and it would be displayed when doing "jest" but not when doing "jest thistestdoesnotexist"?

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