Refactor to Externally Relevant Names / Domain Driven Design

[malcyL]

Version 0.1.0 of this library brought together four public client libraries into one: persona, echo, critic, and babel. Version 0.1.0 of this library brought them together without any significant change to the code from the existing individual libraries.

Moving forward in version 1.0.0, we should refactor away from internal Talis project names and instead use externally relevant names, for example, ListReviews and Files. We may also want to refactor to a more domain driven design rather than the current service driven design.

[junglebarry]

A little context from conversations:

• the service-driven design is that the structure of the library code reflects the structure of the services, which we understand internally, but may have little meaning to customers.

• moving to a domain-driven design means couching the library in terms of common tasks that are meaningful to customers and end-users (which may actually span multiple "services" in the architecture).

It's fair to say that the aims of the library may have changed, and we may be fine with service-driven if they're only used internally. We now have customer-facing APIs that are more domain-driven by their very nature, and domain-driven works well for the application APIs.

We should only consider making the move to domain-driven if there are compelling use-cases for it.