Added JSCS and extended JShint options for a more consistent codebase

I havn't changed the ```spec/``` folder yet, but it runs through the original jshint setup.

This should keep the code base more consistent in terms of coding practices and is a bit stricter on language usages.  The big thing that really diverges from the way dc.js currently does things is adding brackets to ```if``` statements and consistent use of single quotes instead of double quotes.  Even though the one-liner ```if```'s are less code and the d3 examples use this practice; adding brackets is easier to read, but ultimately it's more maintainable.  Single quotes is because I'm lazy on holding the shift key.

Feel free to change the options though, they may be a bit opinionated.

JSCS spec is a slightly modified Google best practices:
https://github.com/mdevils/node-jscs/blob/master/presets/google.json
https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml

Indent remains at 4 and line length is 120.

Lots of files were touched, all spec tests still pass.  The web/stock.js example was touched as well, so that test will fail unless it's updated.