Improve Docker + Decouple HURUmap Dashboard

[DavidLemayian]

Description

We are able to greatly increase the re-usability and development of the HURUmap package by cleaning up how we handle Docker and and its "re-usability of package".

These changes seek to:

1. Create a codeforafrica/hurumap image that installs all the requirements including hurumap.
2. Version hurumap image according to the package's own version (see release.sh).
3. Decouple hurumap.dashboard Django app such that it relies on hurumap instead of other way around.

Fixes #161711666

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] This change requires a documentation update

Screenshots

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation

---

Integration + Other tasks

• [x] Improve data loading
• [x] docker-entrypoint / docker-compose for hurumap.dashboard
• [x] HURUmap Apps
• [x] Takwimu
  • [x] HURUmap Dashboard

[phillipahereza]

@DavidLemayian can we have docker automatically load fixtures?

[DavidLemayian]

@ahereza Definitely not. That would reset the DB on deploy and we don't want that to happen in production. All things that touch the DB must be done manually and intentionally.

[phillipahereza]

@DavidLemayian I think this PR is ready, whenever you're comfortable with it, please release as v0.1 cc @kilemensi

[DavidLemayian]

@phillipahereza I've merged this but on releasing v0.1, that's on you and @kilemensi to:

1. Create a branch for the release
2. Change versions and add documentation
3. Create draft release based on the branch on here
4. ?