Continuous integration - jshint & jscs

Hello Casey,
this is a little follow up to my ATP feedback from yesterday (about the importance of automatic codestyle checking with continuous integration). I configured the [jshint](http://www.jshint.com/) and [jscs](https://github.com/mdevils/node-jscs) tools to check Camel source code. I hope I chose sensible settings -- I tried to stick to the current style of your code assuming this is what you want it to look like. I only fixed a few warnings produced by jshint that (I assume) will result in safer code.

I also added [Travis CI](https://travis-ci.org/) configuration. It automatically runs the checks on every push and on every pull request. If you will make use of this pull request, you should sign in at  [travis-ci.org](https://travis-ci.org/) and configure the automatic builds. The result will look like [this](https://travis-ci.org/ondrejmirtes/camel) (builds of my fork this pull request is from). The badge in README will appear once you configure the build.

If you add tests to Camel one day, you can run them in Travis as well.