Separate test and development gems

Primarily to avoid loading factory_girl in development mode because
it breaks the ability to setup a new database. However, this will
also speedup boot time in development mode by not loading gems which
are not needed.
Merge branch 'gemfile1' into rails408

* gemfile1:
  Separate test and development gems

Conflicts:
	Gemfile
Roll back on sass-rails version

Why? Because we need a newer version of sass. Though it does not
make sense, the older sass-rails gem had a looser version specification
for sass, and so by rolling back sass-rails we allow bundler to choose
a newer version of sass itself.

sass 3.3.x is required because sass 3.2.x fails to parse MarkUs scss code.
Fiddle with the routes some more

Need to allow posting for most of the "match" cases. Need to
explicitly allow :all HTTP methods for the 404 page.
Silence the secrets file warning with a default secrets file

Test and development secrets are not likely to be important, so they
have been given stub values for now.
Fix security warning from Rails 4 related to regepx anchors
Fix various ActiveRecord deprecation warnings

These were all blocking the ability to setup a fresh database.