Fail pipelines which fail prettier code formatting standards

We have not been enforcing our code formatting standards with prettier largely because over a third of our codebase has not yet been updated to that standard.

Let's "prettify" the remainder of our frontend codebase and then make this a hard failure in CI once we're done.

Steps

1. Prettify all CE-only javascript modules which won't cause conflicts with EE in large batches
2. Prettify all EE-only javascript modules in large batches
3. Prettify remaining files (which have EE-specific changes) one at a time or in small groups to reduce burden on reviewer
4. Make a decision regarding prettify standards and our SCSS stylesheets and either prettify them or exclude them from our tooling
5. Ensure running yarn prettier-all no longer produces any changes in the repo (e.g. we've reached 100%)
6. Enable a check for prettier violations within the static-analysis job in CI