Maintenance: update webpack and other dependencies

[pjanik]

https://www.pivotaltracker.com/story/show/185545046

This was necessary, so we can deploy and release this project again (Google Analytics update).
It's not perfect, as now there are some warnings about THREE.js and OrbitControls (that's why I had to disable dev server overlay), but there's no time to make a proper update and migrate THREE.js ~50 versions (from v102 to v154).

@kswenson, sorry for the random review request, but I think there's no one left in the orange team now 😉

[kswenson]

👍 LGTM -- a PT story to clean up the remaining issues at some point (e.g. --legacy-peer-deps) might be a good idea so they don't get forgotten.

[pjanik]

Frankly speaking, I don't think there'll be time or will to do that, as I don't think there are any new features coming. This was just about updating Google Analytics tag. But if there's any round of development, then yes, we definitely need a few days of typical maintenance.

Re --legacy-peer-deps - I think we should get used to that flag. This is exactly what was happening in old Node/NPM versions, and I think it's still better to move to more recent versions and use legacy mode than keep using old Node and pretend there's no problem, as there's no warning (this version conflict is still there, just not announced 😉).