[remove-jeweler] Removed Jeweler from the Gemfile and stock Rake tasks

Jeweler usually puts something into your "Rakefile," but I had split
that out into rakelib/jeweler.rake.
[remove-jeweler] Added instructions for dealing with reveal.js (as submodule)
[remove-jeweler] This is the core of the removal

* Gemspec is no longer generated
* Gemfile just does 'gemspec'
* Also: locked onto haml 3.1: was failing specs
[removing-jeweler] Removed VERSION

(..it's a Jeweler thing)
[removing-jeweler] Added Rakefile, Gemfile to files with Gemspec

I'm not sure if these are needed, but they're relatively small, and I
don't see the harm?

They were included back when Jeweler was in charge-- so, essentially
leaving well enough alone.
[removing-jeweler] Bumped to 0.1.2

Whether using Jeweler or not, I previously had a runtime dependency on
haml, but this really needed to be haml ~> 3.1.x. As it stands right
now, if you grab reveal-ck 0.1.1 from rubygems and do a fresh bundle,
you'll grab haml 4.x and things don't work.

So-- there are no new features or traditional bug fixes in 0.1.2, but
it should be back to normal again.
Started using basic bundler for gem management.

Merge branch 'removing-jeweler'