Apply formatting to vendor/wp-now files

[fluiddot]

Related to #510 (comment) and https://github.com/Automattic/local-environment/pull/198#discussion_r1540910017.

Proposed Changes

wp-now files were ignored in Prettier until we made a decision on what formatting to use (they are formatted with this configuration). My proposal is to use the same Prettier configuration we have in the project. However, this implies updating most of the files.

Testing Instructions

• This PR only re-formats the files so it shouldn't produce any change in the logic. Hence, we don't need to test anything specifically, we could simply run a short smoke test.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wojtekn]

How will it influence future work on merging wp-now changes from the external repository to the studio?

[fluiddot]

How will it influence future work on merging wp-now changes from the external repository to the studio?

Good question. It will require re-formatting incoming files, which is likely to produce file conflicts. However, at this point with all the tweaks/updates we've made to wp-now files, I wonder if we'll consider updating it from the external repository. My perception is that the current wp-now version used in the Studio app has diverged from the original version.

Besides, wp-now might be replaced with Playground CLI which offers quite similar features. Since Playground CLI will be more maintained and updated than wp-now, maybe we could consider adopting this package instead.

[fluiddot]

[...] It will require re-formatting incoming files, which is likely to produce file conflicts. [...]

For re-formatting all files under vendor/wp-now, we can run the command:

• npx prettier --write "vendor/wp-now/**/*.{js,jsx,ts,tsx}".