Fix warning message when there are no tests

[kaykayehnn]

Summary

When running jest with '--passWithNoTests' but there are no tests to execute, it prints a superfluous warning. This PR removes this warning.

Description

In both screenshots below there are no test files and jest is executed with --passWithNoOptions.
It used to log that it exited with code 1 and a message to use --passWithNoOptions, while it exits with code 0 and the option is already provided.

Closes #8594

Before:

After:

[codecov-io]

Codecov Report

Merging #8595 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #8595      +/-   ##
==========================================
- Coverage   63.24%   63.22%   -0.03%     
==========================================
  Files         272      272              
  Lines       11312    11316       +4     
  Branches     2761     2762       +1     
==========================================
  Hits         7154     7154              
- Misses       3541     3544       +3     
- Partials      617      618       +1

Impacted Files	Coverage Δ
packages/jest-core/src/getNoTestFound.ts	33.33% <0%> (-9.53%)	⬇️
packages/jest-core/src/getNoTestFoundVerbose.ts	0% <0%> (ø)	⬆️
packages/jest-jasmine2/src/errorOnPrivate.ts	0% <0%> (ø)	⬆️
packages/jest-mock/src/index.ts	77.52% <0%> (ø)	⬆️

---

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 3f5a0e8...8af21c7. Read the comment docs.

[thymikee]

Nice! Can you add a changelog entry and a small test?

[kaykayehnn]

Sure! I added a changelog entry and some snapshot tests. While adding the tests I found a simpler way to fix the issue so I'll have to force push the new changes.

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