Reduce tools

[stefnotch]

As a contributor, I find the number of tools a bit daunting. We can do better!

List of tools

• Node: JS runtime.
• npm: Needed for the cts.
• pnpm: Needed for the pnpm workspaces. Needs an extra install step
• Biome: Code linting and formatting. Biome has a VSCode extension. Installing this is almost mandatory.
• Prettier?
• Vite/vitest: Building the project and running the tests. Vitest has a useful VSCode extension.
• Wallaby for even faster test running. This is optional.
• Git Submodules: Used for the wesl testsuite and the cts. Comes with git, but needs extra steps to use
• Eslint seems to still be there for code linting.
• Settings specific to VSCode
• Nodemon, since we don't have a task orchestrator for building
• Markdownlint, though this one is mostly optional. I'm not entirely sure how to run it without installing the markdownlint VSCode extension.
• We have an .editorconfig file, which I have never used, since VSCode requires an extension for it, and the code formatter does almost all of it anyways.
• oxlint is also in there. It also has a oxc VSCode extension.

And there are a few more dependencies which do not require an installation step, such as syncpack.

[mighdoll]

Projects growing in complexity as they grow is natural, and trimming back the complexity where we can is healthy. I'd suggest we add the descriptive information in here to Build-Tools.md, and file specific issues about things we can improve.

prettier I think can go right away, for example. and eslint is on thin ice, but seemed worth running occasionally last time i tried. biome is primary until oxlint proves itself better, and running both biome and oxlint in prepush/ci is a way to keep tabs if oxlint starts to surpass biome. For things like e.g. unifying npm/pnpm for the cts, let's file something specific for that if it's viable, lest we leave #176 clogging our issue lists forever.

[stefnotch]

We should be able to run the cts with pnpm, if we use pnpm import.