feat: automatically add review comments to prettier infractions

[pepopowitz]

Note that the base for this PR is the branch from #2675. When that one merges, it will reset any approvals, and auto-set the base to main.

Resolves #1104.

Blocked by #2675, as it depends on the workflow introduced in that PR. My urgency for #2675 is higher than this one, because that one is more likely to catch issues before our release next week.

Description

This PR moves our prettier check from the build-docs workflow to the check-format workflow, and modifies it to add review comments for all violations. This enables us to more easily format changes in PRs that are submitted through the GitHub UI with formatting issues. (We can commit the fixes through the GitHub UI, instead of someone having to pull the change locally, formatting it, and pushing it back up.)

What it looks when there is a prettier infraction

See #2664 for the prototype.

When should this change go live?

• This change is not yet live and should not be merged until {ADD_DATE} (apply hold label or convert to draft PR)?
• There is no urgency with this change.
• This change or page is part of a marketing blog, conference talk, or something else on a schedule.
• This functionality is already available but undocumented.
• This is a bug fix or security concern.

PR Checklist

• I have added changes to the relevant /versioned_docs directory, or they are not for an already released version.
• I have added changes to the main /docs directory (aka /next/), or they are not for future versions.
• My changes require an Engineering review, and I've assigned an engineering manager or tech lead as a reviewer, or my changes do not require an Engineering review.
• My changes require a technical writer review, and I've assigned @christinaausley as a reviewer, or my changes do not require a technical writer review.

The base branch was changed.