fix: prioritize parser used in the project

[JVBorges]

Summary

Fixes #12929

Right know Jest prioritize prettier deciding the parser who is going to be used for the snapshot and let the parser used in the project as a fallback.

I simple change the logic to prioritize the parser found in the projects prettier config file or editors config. If not found prettier will decide which parser is going to be used.

Test plan

You can test using the reproduction repo from the issue.

[facebook-github-bot]

Hi @JVBorges!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, 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.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[SimenB]

great stuff, thanks!

[SimenB]

https://github.com/facebook/jest/releases/tag/v29.1.0

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