This change is primarily intended to allow models to declare their own
default data, without having to use data migrations. Data migrations
have the downside of being run only once, so e.g. `manage.py flush` will
delete default data wchich will never be restored. Also, I consider it
more natural todefine default data setup on model classes.

In order to achieve that, this adds a generic interface for apps to
register hooks called on several signals, by simply implementing methods
with the same name on their AppConfig instance.

Rationale: django-constance is a bit better maintained and has some
features we need, e.g. injecting config into templates through a context
processor. Also, decoupling the settings definitions from import time
allows us to implement lazy access to the config, so we can later access
them in other variables insettings.py directly.

This finalises the migration to the black code style by applying double-quotes.

https://edugit.org/BiscuIT/BiscuIT-ng/-/jobs/690

Closes #111.

It is buggy because it blocks manage.py if no database is available.