Include binstubs generated by Rails 4

Commit b516ecc added `bin/` to the .gitignore file. Now that Discourse
runs using Rails 4 by default, however, we should include the binstubs
generated by `rake rails:update:bin` in version control as this is the
recommendation of the Rails core team. Additionally, for those wishing
to deploy Discourse to Heroku, these binstubs are actually mandatory
according to [this article](https://devcenter.heroku.com/articles/rails4).

Other binstubs can continue to be ignored.

Signed-off-by: David Celis <me@davidcel.is>
added translations to spanish
Extract queries to keep logic in the Categories Model

This creates two methods in the Category model. This moves the model
logic to the model and just calls the Category class methods in
ListController.

This also adds tests for the two methods created in the Category
model. The motivation for this refactor is the code climate score of the
this class and readability of the code.

 Please enter the commit message for your changes. Lines starting
BUGFIX: allow sorting prior to sidekiq starting
Merge pull request #1912 from davidcelis/include-rails-binstubs

Include binstubs generated by Rails 4
Update client.es.yml
Add memory profiler gem for ruby 2.1
BUGFIX: seen logic was incomplete, you can have user_data and still unseen topic
warning if running an old version of bundler
Remove memory profiler at least until I push a new docker image
oops clean gemfile lock
fix build
simplfying color palette, collecting colors into unified variables
Merge pull request #1924 from awesomerobot/master

simplfying color palette, collecting colors into unified variables
Use GlobalSetting to enable CORS at application level
now that wbr tags are inputted, breaking usernames a bit more natually
FIX: Show the renamed uncategorized name instead of "(no category)"
Add groups list to the poster expansion when you click an avatar while
in a topic.
FIX: Chrome has a bug where if you request the same URL with a different
MIME type, then leave and hit the back button, you'll get the last MIME
type requested instead of HTML. This fixes it.
When creating/editing a category the parent shoudl be none.