Make sure that changing grading cutoffs triggers a save confirmation, and reliable reverting of changes.

Rather than asynchronously saving when a setting is updated, we now
prompt the user to confirm their changes and only persist the data if
they hit the save button. Lettuce tests are updated to expect this
behavior and some new ones are added.

When all settings require an explicit save, this functionality will be
shared between each view (with slight changes, e.g. click handlers.)

Parameterize aws s3 bucket name for forum uploads

Jonahstanley/acceptance tests unique database

Add support for Vagrant install, and switch from RVM to rbenv

This explains why acceptance_static is used

Acceptance_static is used to prevent collect static from using a seed
test.py had its seed removed due to redundancy

Update SASS and Bourbon, add Neat

change log levels on the delete course utility. Otherwise they get filte...

tracking in idashboard should only log json-serializable objects

move setting changes in tests to override_settings

Fix course url link in enrollment emails.

change log levels on the delete course utility. Otherwise they get filtered out in production environments (min set to WARN level)

Ned/fix noisy docs

We used to do it this way, I'm not sure why it was changed.
Our settings files add directories to the path, so we need to
do it here so that names will be importable.

refactor login and enrollment test cases to use the mongo modulestore

Otherwise, `vagrant ssh` doesn't load the rbenv shims, because that line is in
the .bashrc file.

added namee to authors file

fix to problems with uploading files

Windows doesn't differentiate between files with/without executable bit,
so this can't be used to exclude the README file from the migrations to
be executed, when the sources are accessed from a Windows partition.