Pass ActiveSupport::JSON.decode a string and not an IO when interfacing with GitHub API

In older versions (< 4.1) of ActiveSupport, this worked because
ActiveSupport used MultiJSON, which would invoke #read if it
responded to it (https://github.com/intridea/multi_json/blob/v1.8.4/lib/multi_json/adapters/json_common.rb#L9).
However, newer versions of ActiveSupport, starting in 4.1, use
ruby's standard JSON gem (https://github.com/rails/rails/commit/ce4456fde6f45f1abd020cbdeb520d401299e01f),
which expects a String. Reading the IO that #open returns
to us and passing the resulting String to JSON.decode ensures
compatibility with all versions of ActiveSupport.
Fix a bug that kaminari doesn't work with nested param_name

fixes #53 but this bug still appears when kaminari is used on sinatra.
Ruby 1.8.7 doesn't like the new hash syntax...
:disappointed_relieved:
Squash "warning: ambiguous first argument; put parentheses or even spaces"
Change 'previous' to 'prev'

"previous" is treated like "prev" by most user agents(maybe), but since
"prev" is officially listed in the specification:
http://www.w3.org/TR/html5/links.html#linkTypes, it should be used
instead of the long version.
PrevPage and NextPage don't use total pages and per page values
Use NextPage and PrevPage to generate link tags for rel=next and rel=prev

fixes #535, closes #509
Add "describe 'Tag'" block
Variable name 'i' isn't a good name, it represents the number of the page
Issue #310 fixed. Refactored code to use a single method to know if a tag page should be displayed.

310 - Fixed. Need to write some tests now.

310 - Fixed. Need to write some tests now.

Stubbed Specs

All tests are passing
Another attempt to use SVG badges
Properly show the Code Climate badge

[skip ci]
Merge pull request #526 from jimryan/master

Pass ActiveSupport::JSON.decode a string and not an IO when interfacing with GitHub API
Fix faling specs for sinatra 1.4.5
Temorary spec for generator

You can run generator spec by doing:

    GENERATOR_SPEC=true rake spec:ative_record_41

We are doing this because we don't want to make API calls in the
spec. At the same time, we aldo don't want to use fakeweb or something
like that because it causes "you never realize until you go production"
 situation. We had it before and shipped a bug - we are not sure what is
a better solution, but at long as I'm aware of this I'll take care of it.
Allow failures for ActiveRecord edge [ci skip]
bson '1.10.0' doesn't work with jruby, use 1.9.2 for now
Oops :boom:
:disappointed_relieved: