[bug 911831] Add South 0.8.2
[bug 911831] Add initial South migrations

* adds South to INSTALLED_APPS
* adds initial migrations for all Kitsune apps that have models
* adds some inspection hints to things that cause problems
* adds last schematic migration to switch us to South
[bug 911831] Update deployment script with South
[bug 911831] Update db and migration docs for South
Quell south logging during tests
[bug 911831] Fix weirdly failing QuestionsVisits test

This fixes the test_visit_count_from_analytics test by tweaking the code
it's testing.

Here's what I observed:

1. The test passes pre-South with and without a clean db.

2. With the South changes, the test fails only when I do FORCE_DB=1. If
   I run the tests as part of the whole suite or on its own with an
   existing test database, it passes.

3. The crux of the problem is the
   cls.uncached.create(question_id=question_id, visits=visits) line in
   QuestionVisits.reload_from_analytics(). For the case where the question_id
   is for a question that doesn't exist, that should fail with an
   IntegrityError. It doesn't kick up an IntegrityError when running the
   tests with FORCE_DB=1. It does kick up an IntegrityError when you run
   the tests normally.

3. If I add some instrumentation to that test and run the tests with
   FORCE_DB=1, I can explicitly see no Questions and no QuestionVisits in
   the db when the test starts. The test adds three Questions--that works
   fine. It then adds four QuestionVisits which is not fine. It doesn't
   seem to trigger the foreign key integrity problem.

4. South lets you create the db for tests via syncdb or via migrations
   (SOUTH_TESTS_MIGRATE). Switching modes doesn't help.

That's everything I've gathered by fiddling with this.

I have a couple of thoughts.

1. Maybe the way South sets up the db sets some state in the session
   that causes problems in the first run, but since the session is killed
   it doesn't cause problems in further runs? Like FORIEGN_KEY_CHECK?

2. I'm missing some important piece of the big picture.

I don't really have time to fiddle with this more and I'm inclined to
think this particular problem isn't that big a deal. Ergo for now I'm
just tweaking the reload_from_analytics() code to check for the question
first which fixes this test when running with and without FORCE_DB=1.
Update db strings.

This just gets rid of the strings for the old topics.