fix: race condition causing GZIP corruption on restart

[yetval]

Fixes #481

As requested, here's the fix for the restart race condition. Found some more bugs on the way:

• Build now writes to views/dist-new and atomically renames to views/dist on completion, eliminating the window where the server could serve plain HTML with a gzip Content-Encoding
• npm run kill now uses npx pm2 kill; pkill -f "node backend.js" || true instead of pkill node, which was killing the pm2 daemon and leaving nginx with stale connections
• Skip paintSource on vendor scram bundles to fix intermittent esbuild failures on repeated builds

[QuiteAFancyEmerald]

After further testing this did not seem to resolve the issue. npm run kill also shouldn't be replaced since its current behavior makes sense versus killing all of pm2 on the VPS. Made some corrections that broke scramjet assets as well. The rename feature is essentially the only thing leftover. As usual the solution is before so I am opening the issue again.

GZIP Gibberish Fix:

• Delete node_modules
• Delete /dist

npm run kill
npm run fresh-start
sudo rm -rf /var/cache/nginx/* 
sudo nginx -t 
sudo systemctl reload nginx