ci(fmt): add formatting regression tests to the `e2e` test harness

With formatting, the more checks the better - adding all the projects within should_pass to fmt checks is a decent way to stress test the formatter and keep it from regressing.

> My thinking is that, we know they should already at least always be parsing successfully, so we should be able to reliably check their formatting too.

_Originally posted by @mitchmindtree in https://github.com/FuelLabs/sway/issues/4192#issuecomment-1461392582_

Locate the `e2e` test harness and its `should_pass` project set first. Extend the formatting checks to cover every project in `should_pass`, then verify the harness catches formatting regressions while preserving successful parsing.

Written by the indexing model from the issue text.