To avoid the large diff can we keep the tab width to 2 spaces?

I actually feel pretty strongly that we should take this opportunity to just go all in on the defaults of our code formatter. Every setting we change is a bit self defeating, when the purpose of the tool is to eliminate code style discussions.

I'd be ok with doing the tab transition in a separate PR to make this one more reviewable, but I think the plan should be to stick strongly with the defaults. As a bonus, we use tabs in our Go code becausego fmt doesn't even have an option to use anything else, and this would be a nice bit of consistency to gain.

✅ Meticulous spotted zero visual differences across 1412 screens tested:view results.

Meticulous tested526/900 of the executable lines edited in this PR¹.

_{1. These lines will likely automatically gain test coverage over the coming days, however if you wish to increase coverage immediately you can do so by interacting with your feature on localhost.}

_{Expected differences?Click here. Last updated for commit075c3be. This comment will update as new commits are pushed.}

@aslilac We can addbiomejs.biome to.vscode/extensions.json and configure some biome related settings in.vscode/settings.json. There are alsoeslint settings there that should be cleaned up.

You can ignore whitespace changes in diffs (in GitHub too) so no harm to reviewability if we want to change the indentation now imo

You can ignore whitespace changes in diffs (in GitHub too) so no harm to reviewability if we want to change the indentation now imo

This PR was just already massive. 😅