Update batman-rails so we can help people get started with Batman [WIP]

> Batman.js

> A client-side framework for Rails developers.

> Batman.js is a framework for building rich web applications with CoffeeScript. App code is concise and favors convention over configuration, and packs a powerful system of view bindings and observable properties. The API is designed with developer and designer happiness as its first priority, and while it has no real dependencies, it works quite well with Rails.

The goal of this Pull Request is to make it easy for Rails developers to use Batman by building conventions.

I'm working on updating the `batman-rails` gem so that we can provide an easy install path for Rails developers. @nickjs @craigdavey and I have talked through how we want to layout the default Batman app when using Rails. I've compleatly rewritten the gem but used a lot of the existing tasks that @jduff had written. Everything has been revisited. In doing so @nickjs, @kristianpd and I are leaning towards avoiding working on the test suite such that I can move forward working on other really important improvements.

In this commit I'll also be taking ownership of this gem and bumping to `0.1.0`. In order to do this I'll need to be added to the rubygems project.

**TODOS**
- [ ] Get rid of Ruby's yeild in the layout
- [ ] Don't remove index.html but add to the readme
- [ ] Application Controller
- [ ] Change view prefix to `pathToHTML`
- [ ] Use Push State as default in Batman
- [ ] Main controller
- [ ] Main HTML directory
- [ ] Content for main/index.html
- [ ] More route examples
- [ ] rails g batman:controller posts index show edit --> should make HTML files for index, show and edit <-- these should contain default HTML "Find me in app/assets/batman/html/posts/show.html"
- [ ] When calling rails g controller don't pluralize
- [ ] No Shim option
- [ ] jQuery option
- [ ] Output after app creation

/cc @jduff