Conversation History Refactoring - Clean Architecture

[milkdromeda]

While conversation history use cases mostly follow clean architectures, the following violations can be addressed:

• The Input Boundaries are used directly. To fix this, a controller should be used. This passes the responsibility of packaging the input data from the client to the controller.
• The view depends directly on the presenter. While this may not violate the dependency rule, it follows convention to invert the dependency, such as by using an observer pattern mentioned in issue Conversation History Refactoring - Design Patterns #39