Enable the use of copied production data in non-production environments

[gsidebo]

In order to test for proper functionality in production, we are looking to build a process around making copies of production data available to -ci and -rc builds. This will give us more confidence about the functionality of the app in production than just using seed data.

GENERAL OVERVIEW:

• We will create production data dumps on a schedule (perhaps once per day). We won't worry about executing new production data dumps on demand for the time being.
• We want to scrub the copied production data for any personal information (at the time of dumping from the database if possible, as opposed to dumping the data and scrubbing it after it has been stored).
• We want this to be 'push-button', ie: a developer should be able to load prod data into a local or external build database on demand. For the time being, we won't worry about automatically loading scrubbed prod data as part of the deployment process.

ISSUES:

• [ ] https://github.com/mitodl/micromasters/issues/2317 (Scheduled process to create prod data dump and put on S3)
• [ ] https://github.com/mitodl/micromasters/issues/2342 (Configure PR builds to use their own indices & create routine to clean up old indices)
• [ ] https://github.com/mitodl/micromasters/issues/2318 (Routine/credentials to load prod-like data into database)
• [ ] https://github.com/mitodl/micromasters/issues/2065 (Anonymize prod data)
• [ ] https://github.com/mitodl/micromasters/issues/2343 (Research: Preserving specific local data after prod data has been loaded)

[pdpinch]

I just changed the order a bit and moved #2317 and #2342 into ready. I think those two will give us some initial value and we can address the rest as time allows.