Node specs

Opening this up for discussion if anyone is interested.

Basically, pulls in grunt-jasmine-bundle and sets up two suites (unit and e2e). 

Unit is going to be pretty straightforward and will probably focus on leaf node's in Lineman's object graph that have somewhat meaningful logic in them. Unfortunately, because of how much firect file I/O goes on, we'll either need to introduce adapter shims (good thing) or we'll want to settle for murkier more integrated-y specs to get that regression confidence (bad thing). Either might be the right thing to do though.

e2e is going to focus on end-user observable behavior. Example: I change a Coffee file and see it in the browser. Example: I do something that should result in a change to the grunt configuration and I run `lineman config foo` and read back that the change took place.

This branch is "ready to merge" IMO when we can delete the ruby test suite without a decrease in regression safety.