feat(nx-spawn): Improve dependency execution

[luxaritas]

I wound up rewriting most of nx-spawn to pull from Nx's task runner code. We're now properly running dependencies only once and waiting for build outputs to be present before continuing with other tasks that rely on it.

To make build-watch/serve work properly with this, I've also had to prevent vite from removing the dist directory when it rebuilds - see the comments in the core vite config. I've also made it automatically watch when running in development mode for convinience.

Bonus: I realized that the reason why the package-lock kept getting corrupted from under me was because the npm i in the distify build process was touching it, and incorrectly changing some metadata. I've updated it to use --save=false to avoid this.

Resolves #13
Resolves #23

[tkaragianes]

I'm starting to get a little worried about the amount of plumbing we're introducing. We've got nx and vite, but they're very heavily customized. For me, more documentation about the motivations behind our departures from the norm would be helpful. The code is well commented, but I feel like I'm lacking the why behind some of the choices.