Put node_modules under version control, grudgingly.

This is a "best practice" according to Heroku and this smart fella: http://www.futurealoof.com/posts/nodemodules-in-git.html.  This is because our packages.json only locks in the top-level dependencies.  Lower level dependencies could be different on each deploy, which is clearly a non-starter.  Vendor all the things, bro.
Also track client side apps installed via Bower.

Why not, in for a dime, in for a dollar.
Manage static directory configuration via NODE_ENV
Build our 'dist' folder after an 'npm install' on Heroku via a postinstall task.
Add lodash dependency
Add the lodash-cli package
Add lodash to devDependencies
Try preinstalling lodash on heroku
Try grunt with full local path
Fix Gruntfile env task
Update node and patch versions of dependencies
Track our bower assets too
Track our dist assets.

In for a dime, in for a dollar. Prevents us from having to run a grunt task on Heroku. Right now Heroku deployments are failing due to some strange interaction between Grunt and its Lodash dep.
Get rid of our postinstall
Add a Procfile for Heroku
Remove profanity accidentally deployed…goddamit.