Don't minify during development

[DavisVaughan]

Working in apps/vscode/ currently kind of sucks because the debugging experience is suboptimal. Sourcemaps don't seem to be working right, causing the Debug Variables pane to show minified names, not real names. Stepping is also pretty jumpy.

Turns out that we are minifying during our dev builds, which seems to be what is breaking things. It is also kind of weird right? We should only minify during production, not during development. That's also what VS Code's extension guide suggests:
https://code.visualstudio.com/api/working-with-extensions/bundling-extension#run-esbuild

And what esbuild's guide says: "Usually you minify code in production but not in development."
https://esbuild.github.io/api/#minify

Before:

(Note how the variables pane has 1 letter names, and how it jumps over the if branch, seemingly without running it)

Screen.Recording.2024-10-30.at.12.00.24.PM.mov

After:

fixed.mov

---

In theory both VS Code and esbuild have all the required glue to make minify + sourcemaps work through this names mapping field, but clearly something isn't working right:
evanw/esbuild#1296
microsoft/vscode#12066

[cscheid]

Do we want to split the difference and keep the minify option, but defer to dev if minify is undefined? I'm not sure I want to remove minify before understanding exactly how it could be used.

[DavisVaughan]

I've kept the exposed minify option and instead just set it to minify: !dev, in the two places that we call runBuild() - which makes this an even more minimal fix