Native migrations created with Python 2 differ from ones created with
Python 3. More importantly, they failed when used in Python 3, but not
vice versa. This is caused by field names being marked as byte strings
when using Python 2.

This rewrites the native migrations, which probably isn't a bad thing
either, because they were created with a pre-RC2 version of Django, and
Django 1.7 has since seen a few more migration-related fixes.

It's likely Django now does the correct thing and generates Python 2 and
3 compatible migrations under both versions of Python.

New style migrations created with the helper script. Now doesn't detect
any more changes after this set has been applied.

This change might need to be re-applied if more migrations get added
before this PR is merged into master.

More changes need to be done regarding migrations; this commit just
moves them out of the way so that Django doesn't pick them up.

The initial one is for the releases/0.1 branch - any others are to
handle changes in the 0.2 branch.