Set default RDS PostgresSQL version to 9.3.5

This version is the first version to support read-only replicas with
RDS.
Fix typo
Add basic group detail page

The rough layout was inspired by the wireframes.
Add a form to edit group settings

I followed an often used convention of using /model/{id}/edit/ as the
url for displaying the form. The form POSTs back to /model/{id}/edit/
and then redirects to /model/{id}/ on success.
Merge pull request #112 from jwalgran/topic/group-detail-page-basics

Group detail page basics
Add title field to Event, automatically generate slug

Changed url_name to slug for consistency with Group

Uses the shortuuid library to generate unique 21 character slugs for
private events.
(https://github.com/stochastic-technologies/shortuuid)
Merge branch 'feature/hmc/postgres-9.3.5' into develop
Merge pull request #118 from maurizi/event-slug

Add title field to Event, automatically generate slug
Merge pull request #120 from maurizi/develop

Fix typo
Allow overriding of default Django registration templates

The Django Admin site is before Django registration in the INSTALLED_APPS
list.  Rather than mucking with the INSTALLED_APPS order (which seemed to
have no affect anyways), it seems cleaner to use the filesystem template
loader to pick up these templates
Fix Django Debug toolbar

With nginx in place the REMOTE_ADDR field in the HTTP header is no longer
10.0.2.2, but instead 127.0.0.1
Add some empty templates for use as prototypes

Also cleans up some urls/views:
 - Removed individual mapper page view, this will be on the group settings
 - Added achievement and training pages
 - Moved other instances of group name -> group slug
 - Made all events URLs be under group/<group_slug>/event/<event_slug>
   This is needed because event slug is `unique_together` with group_slug
Merge pull request #121 from maurizi/empty-templates

Add some empty templates for use as prototypes
Merge pull request #109 from maurizi/show-achievements

Show achievements on the user profile page
Enable contrib.gis to allow OpenLayers forms on the Django Admin site

Needed for editing things like Events which contain geospatial data.
Without this in place and without a custom form for editing geospatial,
the Django Admin page will *crash* on models that have Geospatial fields
Merge pull request #119 from maurizi/enable-contrib-gis

Enable contrib.gis to allow OpenLayers forms on the Django Admin site
Replace gulp-sass with gulp-ruby-sass

This changeset attempts to resolve #117 by replacing `gulp-sass`
(`libsass`) with `gulp-ruby-sass` (Ruby Sass). The main tradeoffs are that
Ruby Sass can be slower than `libsass` and requires the Ruby runtime,
but Ruby Sass also appears to be more stable, doesn't require the Node
bindings for `libsass`, and has all of the Sass features.

Arbitrary data points around build durations:

**gulp-ruby-sass**

```
./scripts/npm.sh run build-debug  1.29s user 0.27s system 30% cpu 5.042 total
./scripts/npm.sh run build-debug  1.28s user 0.27s system 31% cpu 4.957 total
./scripts/npm.sh run build-debug  1.29s user 0.27s system 31% cpu 4.955 total
```

**gulp-sass**

```
./scripts/npm.sh run build-debug  1.42s user 0.31s system 32% cpu 5.394 total
./scripts/npm.sh run build-debug  1.39s user 0.30s system 31% cpu 5.370 total
./scripts/npm.sh run build-debug  1.39s user 0.30s system 32% cpu 5.155 total
```

Sass test file:

```scss
$font-stack:    Helvetica, sans-serif;
$primary-color: #333;

body {
  font: 100% $font-stack;
  color: $primary-color;
}
```

I assume that as the amount of Sass piles up, the performance benefits
of `gulp-sass` would breakthrough. Not sure though.
Switch from npm module to calling npm directly

A new npm package, `gulp-ruby-sass`, was added in 7de060d.
The npm ansible module appears to not have picked up this up, and
`gulp-ruby-sass` was not installed.

Switching to calling `npm install` directly did install the package.
Add NPM shrinkwrap file

This helps lockdown the versions of a package's dependencies so that
we can control which versions of each dependency will be used when
`npm install` is run.
v8flags consistently failing clean VAGRANT_ENV="TEST" provisions

Reverting to v1.0.1 resolved the issues. v8flags `CHANGELOG` below:

  2014-09-03 - v1.0.0 - first major version release
  2014-11-17 - v1.0.2 - get node executable from process.env._
  2014-11-17 - v1.0.3 - get node executable during npm install via
                        process.env.NODE
  2014-11-18 - v1.0.4 - wrap node executable path in quotes
  2014-11-26 - v1.0.5 - get node executable from process.execPath
  2014-12-09 - v1.0.6 - revert to 1.0.0 behavior