Description

Every version bump in prettier has a chance to change the desired output and thus break our linting. This PR changes it back to a specific pinned version instead of letting npm and semver take over.

Specifically a recent change in 3.5.0 was a "breaking" change for us and changed the desired format of a css file we haven't touched in a a while. It looks like @jjhembd addressed this in 1c892c8 so merging main will work but branches may be "outdated" and break in CI.

We should keep the prettier version updated so we don't have to do as many big refactors like #12206 but it should be intentional instead of randomly when people run npm install or when CI installs a different version than people have locally. I did check and pinning the version still has it show up in npm outdated so the release process should still catch it.

Issue number and link

no issue

Testing plan

• rm -rf node_modules
• npm install
• npm run prettier-check should pass

Author checklist

• I have submitted a Contributor License Agreement
• I have added my name to CONTRIBUTORS.md
• I have updated CHANGES.md with a short summary of my change
• I have added or updated unit tests to ensure consistent code coverage
• I have updated the inline documentation, and included code examples where relevant
• I have performed a self-review of my code