chore: use prettier more

[tatomyr]

What/Why/How?

Ran Prettier on yaml and json files.
I believe we'll benefit from enforcing consistency wherever we can automate it.
Changes mostly located in test files, so I also updated the snapshots.

Also I'd suggest covering .md files after merging large docs MRs.

Reference

Testing

Screenshots (optional)

Check yourself

• Code is linted
• Tested with redoc/reference-docs/workflows
• All new/updated code is covered with tests

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

[github-actions]

Command	Mean [s]	Min [s]	Max [s]	Relative
redocly lint packages/core/src/benchmark/benches/rebilly.yaml	1.759 ± 0.035	1.695	1.819	1.02 ± 0.04
redocly-next lint packages/core/src/benchmark/benches/rebilly.yaml	1.716 ± 0.054	1.662	1.834	1.00

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	73.29%	3506/4784
🟡	Branches	64.93%	2003/3085
🟡	Functions	65.66%	589/897
🟡	Lines	73.35%	3264/4450

Test suite run success

587 tests passing in 85 suites.

Report generated by 🧪jest coverage report action from 4d9df11

[lornajane]

I really like this! But how can we maintain the standards on the project? I think having it as a precommit requirement might be too much for a public project, do we or could we run the check task in CI?

[tatomyr]

@lornajane yeah, the same task in CI we're currently running for ts/js files, but extended for yaml/json. See the changes in package.json: https://github.com/Redocly/redocly-cli/pull/1109/files#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R18

[lornajane]

Thank you @tatomyr (and prettier!). A good quality improvement IMO.