[Request]: SDK: Investigate cleaner organization of client API.

[jglogan]

Feature or enhancement request details

Right now the client API organization and implementation is a bit scattershot. Investigation tasks:

• Examine organization of client, server, and domain type code for ContainerClient and the services (API, plugin, image, container, network, volume). Some client types are defined by services while others are defined by ContainerClient. The image service target might have the best organization.
• Examine where redundant types can be eliminated and common patterns established for configuration-vs-runtime state. Currently, each resource does this differently.
• Examine dependencies between ContainerClient and services to see whether there's a more sensible arrangement.
• Examine where docc is lacking on the client API surface.

Code of Conduct

• I agree to follow this project's Code of Conduct

[jglogan]

Created #1020 which addresses the first (project organization) and third (library and dependency organization) tasks from the list.

Once this issue is closed we'll create new issues for docc gaps and for further refactoring (breaking up the monolithic Parser and Utility types into resource-centric operations comes to mind).