Switch build system from Python/Java to pure JavaScript/Node/NPM.

As per the discussion here:

https://github.com/mrdoob/three.js/commit/9b8db498c8579763bf2dc7eebf4d40f9c891ac85#commitcomment-2471094

I have removed the Python-based build.py and the Java-based Closure compiler. I have also switched all build*.* scripts to call "node build.js" instead of "python build.py."

This unifies Three.js so that both its library and its build system are written in JavaScript.  It does not significant change the results as we were not using the advanced features of the Google Closure Compiler.  See here for size comparison between the Closure Compiler and Uglify2:

https://github.com/mrdoob/three.js/commit/9b8db498c8579763bf2dc7eebf4d40f9c891ac85#commitcomment-2471573

I have modified build.js to give better error messages when "npm install" hasn't been run and I have added a README.md explaining how to get the build system up and running:

https://github.com/bhouston/three.js/blob/c2928a71c3981031ecafa71e8de1eb6e2ad9e62f/utils/README.md

I am okay if this get's rejected, but I do think it is a simplification of the build system.

All examples still run without errors.