refactor: Bump prettier from 2.0.5 to 3.5.3

[dblythy]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: #9625

Approach

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)
• Add security check
• Add new Parse Error codes to Parse JS SDK

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[codecov]

Codecov Report

Attention: Patch coverage is 91.57895% with 8 lines in your changes missing coverage. Please review.

Project coverage is 93.08%. Comparing base (042a920) to head (ac2c36e).

Files with missing lines	Patch %	Lines
src/SchemaMigrations/DefinedSchemas.js	55.55%	4 Missing ⚠️
src/Auth.js	75.00%	1 Missing ⚠️
src/Controllers/SchemaController.js	90.00%	1 Missing ⚠️
src/Routers/GraphQLRouter.js	0.00%	1 Missing ⚠️
src/middlewares.js	92.30%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha    #9671      +/-   ##
==========================================
- Coverage   93.10%   93.08%   -0.03%     
==========================================
  Files         187      187              
  Lines       15016    15044      +28     
==========================================
+ Hits        13981    14003      +22     
- Misses       1035     1041       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mtrezza]

What did this PR require? Only upgrading the dependency? I thought it was more because the definitions check failed.

I assume all the other changes are because you ran lint:fix?

[dblythy]

I upgraded the dependency and ran prettier + lint

[mtrezza]

I think we need to be careful running prettier across the whole code base. It could disrupt existing PRs, because the rebase may be difficult. We also have no automation in place to ensure prettier before merge, so this is a continuing cicle. A pre-commit hook is not a good solution. I'd suggest to run prettier --check in the CI, just like we do for lint.

Interestingly, I ran npm run prettier && npm run lint-fix and get many changes. I think it's unlikely that they all come from the last few alpha merges: