Using bower to manage external libraries.

This is a pretty big change code wise, but in practical sense is fair simple.  It changes the management of external libraries to using [bower](http://bower.io/).

Bower allows to manage dependencies and helps better keep track of where things came from.  This means it will be easier to update the external libraries.

This also adds for future features such as making this application more of a module than a deployable/forkable application.  At that point, it may make sense to not commit the bower_components directory, but for now, it makes sense.

It also means that if you use proper version tags and keep bower.json file up to date, it will be easy for people to install specific versions.

It will also allow for taking the Gneiss chart library out and making it a standalone module (more easily, at least).

The only really change to do as managing the repo is both use git tags for semver version numbers (I set the bower.json to 0.1.0 but you can update as needed), and then actually manage any updates to libraries within the bower.json file.

Oh, and it looks like you hacked Sugar.js given the name of the file, so that is still managed in the JS file.  I would highly suggesting forking Sugar.js to make your changes and then managing it through the bower.json file as this allow for better understanding of what you changed and allows for your changes to go upstream if they make sense.