Finally kill the configure task!

Pour a shot, @davemo
register the default task to an empty array. 
Leaving it undefined has unintended consequences
when running `lineman grunt` without a task.
Fixes #112
Merge pull request #113 from testdouble/adds-command-chaining

Adds command chaining
Print out help if the user only enters `lineman`
Implements a nifty `config` reader

This action is designed to facilitate scripting
lineman based on its configuration.

The first bit of usefulness will be to verify 
Sass is enabled before we go about installing
the bundler & sass gems in our heroku build path.
One can do that like this:

```
$ lineman config enableSass
false
```

This config will follow '.' properties in the app
config, and will even follow indexed subscripts 
(e.g. 'foo[1]')

```
$ lineman config watch.pages.files[1]
app/templates/homepage.us
```

Neat-o! cc/@jasonkarns @davemo @theotherzach
0.12.0
Fix the note in the readme

The [] seems to be problematic because it is a reserved syntax for links (AFAIK) so it cannot be bolded (seems so). I think that the note works good without the need of [].
adds js+css to the default pages template context 

This is strictly for backwards-compatibility. If
a user upgrades to the latest lineman from a project
that predates the unification of generated & dist
filenames for app.js & app.css, they'll see a super
confusing white screen. Just ran into this with a 
current user.
0.12.1
Merge pull request #115 from Foxandxss/patch-1

Fix the note in the readme
fixes #46 (finally!)

Reproduced this with a super simple POST request,
was much easier to reproduce once we knew that
ordering was the issue.

``` ruby
require 'sinatra'

post '/hi' do
  puts params
end
```

Ran that server, connected the bodyParser at the
top of the express setup, then tried this from
console:

``` javascript
$.post('/hi', {wtf: true})
```

And sure enough, it hung forever.

Moved the bodyParser beneath the proxying setup
and it worked fine.

yay!
wtfdebuggershowdotheyworklolbbq
Fix bodyParser() by drawing routes in configure()
0.12.2
Augments app.routes to insert bodyParser
- this approach leaves apiProxy'd endpoints alone, and prevents issues
with the bodyParser messing up proxy'd endpoints
- this allows both proxy'd and stubbed endpoints to exist and operate
in harmony :)
0.12.3
update jasmine-stealth
0.12.4
Add link to 'Using Ember.js with Qunit' to README.md