Worked on #3 got celery running, sample tasks.

Implemented two possible SRS styles, both requiring Celery beats to be
up and running.
1) Each SRS level gets its own scan
2) Bulk scan of ALL levels done in same task, using update() method,
which requires only 1 db hit.
Also made a failed burn drop you two levels.
Will have to profile speed and memory usage.
Fixed a bug introduced while refactoring JS

accidentally wasn't calling wrongAnswer() on wrong answeer.
Added a check in sync_unlocks

makes sure we dont actually create two sets of a review for the same
vocab.
Fixed all_srs

correctly zips the times and the streak numbers for SRS checking.  Also
wrote tests for tasks and views and models.  Added a distinct() to
ensure we don't grab doubles, as for example, reading__level could
return duplicates for the same vocab object.

Fixed major bug in UnlockRequested, my get_or_create was passing in
needs_review=True, which was causing it to create duplicates, one with
True, and the old one with false. This leads to users having two of the
same vocab in the review. big nono.
SRS Setup on schedule, minor tests added

- Added CeleryBeat schedule for SRS.(Once a minute)
- Added a "Refresh" button to Home page, forces an SRS update for the
user.
- Fixed a minor bug in all_srs which caused the logging to always say
there were 0 reviews.
- Fixed a major bug where it would also query reviews that had been
previously flagged for review.
- Force-review check returns the total number of reviews to be done
after the check.
TODO: write some js that fills in the Reviews button based on the
force_srs ajax response.
SRS schedule Working

Also, I managed to fix up logging quite a bit. Files held in logs/*.log
however that's in the gitignore for now so we dont spam logs.