Utilize Docker Socket/TCP API Instead of Local Binary

Currently, `lazydocker` supports only local docker management by directly interacting with the locally installed `docker` CLI binary. This also means, running it inside a container (as per #36) would require packaging the CLI binary in it. By utilizing the HTTP API exposed by the Docker the tool can easily be configured to work with both local and remote Docker instances.