Extensions via entry points

- auto-loading of modules in the 'docker_registry.extensions' entry
  point group
- preliminary documentation
- define and encourage API on top of signals and config

This is an alternative approach to import_modules (#565) and namespace packages (#566).
Is your extension living under docker_registry/extensions? (eg: if we opt-out of namespaces, we don't want that)