Separate the reporting suite front end (Flask application) from the backend.

[KevinFasusi]

Currently, the core logic and the reporting suite are in the same library, separating the two components of the project will:

1. Help maintain the orthogonality of the codebase and keep the code decoupled. Fixing bugs, making enhancements in either the core logic or the reporting suite should not have side effects.

2. Make it easier to work on the project in smaller sprints.

3. Make it easier to document.

4. Allow dependencies to be precise.

5. Remove the requirement for a full release of the library when bugs get announced in dependencies for the frontend (some javascript libraries).

6. Make it easier to contribute to the frontend by reducing the need for domain knowledge. I spoke with a UX/UI company about the reporting suites and summarised the responses in this blog post.

7. Improve the test coverage and completeness. The current test suite does have unit tests but not functional tests (there are a few basic ones).

8. Help keep the codebase Pythonic and reduce technical debt and "code smells".

These are some of the main points I think make separating the project a sensible decision. If there is anything else to consider, please comment.