Move event-related models from 'cof' app to 'gestion' app.
Add 'Association' model to register name, related groups (buro,
members), etc.
Club is now associated with a single Association instance.
Migrations take care of these changes.
Profile view
- Let the user see his information.
- List the clubs whose he is a member.
Profile edition view
- Renamed from previous "profile" view
- User can now change "occupation" field.
Club detail view
- Informations about a club.
- Accessible by staff members and "respos" of the club.
- List members, with subscription fee (if applicable).
Club admin
- Change memberships of clubs added.
- Mark more strings for further translations
- in verbose names
- in the __str__ method
- Turn all verbose names into lowercase
- Add more verbose names
- Set an ordering on gestion.EventCommentField
- More database constraints on EventCommentValue
- `TextField` is not nullable
(https://docs.djangoproject.com/en/1.11/ref/models/fields/#null)
- `unique_together` constraint on the two fk
- The models are moved to the `gestion` app
- A new field `associations` is added
- The location and datetime fields are removed in favour of a new model
`EventTimeSlot`
- The old events are migrated to the new app and linked to the
`cof_buro` association
- Move the model
- Add some BDS-related fields
- Add an `associations` fields to be able to separate the clubs between
the different associations using groups
