Increase connection_pool, configure reaper

When multiple workers attempt to join/communicate at once the pool is being exhausted.
There's also no sense in waiting for 5 seconds since we're on a good connection.
If it can't get one immediately, it should give up. Also configure the pool
reaper in case a thread happens to leak a connection.
Don't include CloudCrowd into Kernel name-space

CloudCrowd's constants such as PROCESSING, FAILED, COMPLETE, etc where
polluting the namespace and leading to confusing when the console was used.

This moves only the relevant classes into the Kernel name-space
for easier querying while leaving everything else defined only
under CloudCrowd.

It's a pretty gnarly hack, but is only used in the console, so... yay?
Make ProcessingJob a belongs_to for easy retrieval
Clear X-Frame-Options for iframe_success action
Clear X-Frame-Options for iframe_logout action
Remove old Rails 2.3 remnants

Have been on Rails4 for a few months now, don't think we'll need
to readily refer to them any further.
Re-add binstubs to repo

Not sure what's changed, but they seem to play fine with both chruby and rvm now.
Before we had problems where the incorrect ruby would be selected.
Additional `raw` missed.
Use pry for debugging in development
Set RAILS_ENV from ARGV before initialization

The Rails.env defaults to: `ENV["RAILS_ENV"] || "development"`

There are numerous spots in the Rails code-base that cache the value inside strings and they're called before the rake
tasks are.

This means that when a rake task kicks off, the environment is already set and is really impossible to change inside of a
task chain.

This presents a problem since our tasks use the format of "rake <environment> <task>"  The environment task would appear
to succeed, but wouldn't change all aspects to reflect the environment, leaving some things still referring to
development.

This checks to see if the environment is set as the first argument and sets the ENV to reflect it before requiring any
Rails code.
Update sunspot_rails to silence json deprecation
update css for disabled roles.
Missed comma to separate test and development
Fix yaml erb file.
New deploy:minimal task

This task only pull in new code, restarts the server and warms it.

Unlike the other tasks, no clearing of caches is performed.
Use NET::SSH::Shell for deployment

This creates a "real" login shell that has the correct
environment for running commands that require chruby.

It also multi-threads the connections for parallel multi-host deploys
Do not run jammit as www-data user.

The sudo was needed in the past so the assets directory
ownership would be correct, but isn't an issue now.
Complain if RAILS_ENV != the rake environment

Just in case someone attempts to run:

  RAILS_ENV=production rake staging task
Use backticks instead of sh for commands that fail

If the directory doesn't exist (like on staging), sh throws an exception
causing the deployment to fail.

Better to just print the error and move on
Merge branch 'master' into split_access