Allow testMatch for jest config

[favna]

Resolves #8637.

Tested locally with these steps:

1. cd packages/react-scripts
2. yarn link
3. In another project: yarn link "react-scripts"
4. Running SKIP_PREFLIGHT_CHECKS=true yarn test
5. Verifying that nothing changed from before symlinking modules
   
6. Add testMatch key to package.json Jest config
7. Running SKIP_PREFLIGHT_CHECKS=true yarn test again
8. Verifying that only filed matching specified pattern are being included for testing
   

For further reasoning as to why this option should be added please refer to #8637.

[facebook-github-bot]

Hi @favna!

Thank you for your pull request and welcome to our community.We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.

In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[favna]

Failing CI appears unrelated to this PR, as a matter of fact, at time of writing CI is also failing on master....

[mrmckeb]

I see no reason why this would affect the CI either, sorry you hit that issue.

@ianschmitz I think we can merge this one?

[ianschmitz]

Bah this error in CI is getting old...