Build out unified CLI system for interacting with resources

[alexkreidler]

We need a Kubectl-like API to interact with:

• Managers - a daemon or tool to manage pipelines
• Executors - an environment which runs the Wiz Executor or other processors
• Pipelines - the logical pipeline, a graph of connected processors
• Processors - an individual operation which processes data
• Registries - an endpoint/API/server that contains a set of packages
• Package - a logical Wiz Package

all of these should be able to be created, deleted, viewed, and possibly modified via the CLI.

Some of the commands may be aliased for ease of use but they should all have their own sections.

With Kubectl they chose get <resource>, create <resource> because each resource is just an HTTP endpoint/object that has the same CRUD API on the API server.
Docker however chose <resource> create etc because each resource is managed differently

Since our resources are heterogenous and may be interacting with different client API libraries, API specs, and endpoints, we should be careful about this. Additionally, some resources may not support all operations.

[alexkreidler]

Serve both JSON and Protobuf where possible, generic system for API types. Use kubernetes/code-generator and api-server as inspiration. api-server uses go-restful