Add another suggestion field to submissions

Part of evernote/pootle#163

Pick note: Regenerated the whole migration.

Conflicts:
	pootle/apps/pootle_statistics/models.py
Add app suggestion fields to store suggestion

Part of evernote/pootle#163

Pick notes: Did some adjustments to model, including keeping the
    translation_project field, and completely regenerated the migration.
    Recovered SuggestionManager in order to provide the new `pending`
    method.

Conflicts:
	pootle/apps/pootle_store/models.py
Add missing logging

This is from a not picked Evernote commit. It is necessary to get working
one the migration in the next commit.
Merge suggestions (evernote/pootle#163)

- Move all pootle_app.Suggestion data to pootle_store.Suggestion
- support new Suggestion schema where old pootle_app.Suggestion(s) were used
- Save reviewer when accept a suggestion
- Get pending suggestion for a Unit only
- Get translation_project for suggestions from unit joined with store
- Cleanups
- Update last action when accept and reject suggestions

Pick notes: Made adjustments to the migration to match our models and to
    include the translation_project field that we also included in the
    new unique Suggestion model for showing contributors list. Also did
    other adjustments to alter code that Evernote no longer has. Other
    changes were necessary to fix issues with code that diverged.
    We didn't pick the changes for saving the store when creating
    Submission objects.

Conflicts:
	pootle/apps/pootle_app/management/commands/refresh_stats.py
	pootle/apps/pootle_profile/models.py
	pootle/apps/pootle_project/models.py
	pootle/apps/pootle_statistics/models.py
	pootle/apps/pootle_store/models.py
	pootle/apps/pootle_store/views.py
Followup: rely on Suggestion's translation_project field

We kept it to simplify contributors list calculation.
Use Suggestion.reviewer as submitter in accepting and rejecting submissions
Accounts: Use AUTH_USER_MODEL in all User migration relations
initdb: Create directories before creating essential users

This fixes the issue of Directory.objects.root being called before
other models are loaded
Accounts: Use settings.AUTH_USER_MODEL in PootleProfile as well
Accounts: Get rid of is_staff everywhere
Accounts: Add a custom User class
Accounts: Use full_name instead of first/last name
pootle_store/views: Simplify user/profile logic
Accounts: Get rid of PootleProfileManager
Accounts: Get rid of the custom Profile admin
Accounts: Move UserForm to accounts.forms
Accounts: Move User.post_save logic to accounts

This lets us avoid a call to get_user_model() before the app registry is ready.