No more ambiguos root routes

Rails 4 does not like there to be more than one root route specified
unless they are explicitly named.
/script/rails is unnecessary

Rails and Bundler should just do the right thing
No need to require rubygems on boot
Initialize new secret token setting
Move parameter filtering to initializer

This is what Rails 4 does by default
This should no longer be necessary
Scopes should be given callable object
TEMP: Disable test_track gem

Doesn't appear to play nice with Rails 4.
Specify regexp validation as multiline

According to the error from Rails 4 - "The provided regular expression
is using multiline anchors (^ or $), which may present a security
risk. Did you mean to use \A and \z, or forgot to add the
:multiline => true option?"
scoped method deprecated
Fix regexp deprecation warning

Don't use multiline matcher when we mean mstart of string
More deprecation warnings
No need for assert_block here
TEMP: Disable protected attributes

They don't play nice with Rails-4 compatible globalize. Will replace
with strong params where appropriate.
Use Rails 4-compatible gds-sso branch

Current release breaks unless you have protected_attributes
Confirm is now a data attribute
Disable implicit join references

This gets rid of deprecation warning relating to referencing an eager
loaded table in an SQL snippet. Because we don't rely on implicit join
references, we can just disable the feature entirely.
Don't call #all on associations - use #load

Another Rails 4 deprecation
Replace old-style dynamic finder

This replaces old-style dynamic finders that have been deprecated and
also some that don't play nice with the Rails-4 compatible globalize
gem - dynamic finders on translated columns don't work.
Update friendly_id config

Note that this version of friendly_id has a couple of differences to
the previous version:

1) The default sequence seperator used when there is a slug clash is
now a single '-', rather than a double-dash that was used previously.
I've left the config to use the new single-dash, but this can be set
back to double-dash if we deem this necessary.

2) Previous versions of friendly_id appended a numeric sequence to
make slugs unique. The numeric sequence has now been replaced with a
UUID (to simplify the code and make it more thread-safe).

This second change results in very ugly slugs. However, friendly_id
provides a new mechanism to reduce the chance of such clashes by
allowing you to specify slug candidates (see
lib/friendly_id/slugged.rb in the friendly_id gem). I'll explore using
this in a later commit.