migrate build system from browserify to webpack

[hyperupcall]

from issue #22, this migrates the build system from browserify to webpack. this required to two / three main changes

• adding .default to any require'd vue single file components (commit 21a20bee911e5d6d39db5f579ea0aa82a2063e94)
• ensure that __ANALYTICS__ and __DRIFT__ placeholder values are resolved at build time (before webpack build process). (so resolving them was removed from app.js, except in the special case where process.env.RDB_HOST is defined (i'm not sure if this is needed))
• webpack now generates the final html file (i don't think hmr works without doing this) (whereas before it appears that we generated the final html at runtime in app.js). in summary, index.html is processed as such: the starting index.html is at src/static/index.pre.html, and the gulp task static processes it, and writes it to src/static/index.html. webpack uses this, processes it, and writes it to dist/index.html. the gulp task prod copies this to public. i didn't want to add this complexity, but i think i had to, to enable webpack hmr (commit b98c6c19d08c99488deabec4bc60b2b0366fd08e)
• fixed fonts loading (i'm not sure what happened since moving from browserify, but because fonts stopped loading, i had to add a /fonts route for the express server (which resolves to static directory /public/fonts) (maybe there is a better fix i am not seeing?))

i kept the existing gulp js and css pipelines intact, since it didn't seem necessary to rebundle them with webpack

also the prod.js bundle size decreased from 624kiB to 552kiB

i might have missed something, but let me know if you have any questions, or if something looks off, some extra details are in the commit messages :smiley:

[zllovesuki]

process.env.RDB_HOST was part of the legacy code that signifies development environment. That’s was when SlugSurvival was running as one giant monolith. You can safely change that to some other sensible name 😅

Anyway, I will check it out soon. Again, thanks for the work!

[zllovesuki]

I'm trying to see how to best integrate the new build system with CloudFlare's Workers as the frontend is running on CF's Workers.