Allow bi-directional management of containers

[deviantony]

Before k2d version 1.0.0-beta, k2d used to allow bi-directional management of some resources:

As an additional benefit, as the translations are bi-directional, any Docker management commands executed outside of K2D on the docker host directly, are also translated and appear as Kubernetes resources when later inspected via Kubernetes tooling through the translator.

This feature is now partially supported. The user needs to know how to name Docker resources and which labels to associate with them in order to manage these resources using a Kubernetes client.

We want to re-introduce bi-directional management of containers with support for the following operations:

• List pods - kubectl get pods -A, kubectl get pods
  • Listing pods across all namespaces or the default namespace will include the containers created via docker run... as well as pods created via k2d
• Inspect a pod - kubectl describe pods/container-name, kubectl get pods/container-name
  • Allows you to inspect a pod associated to a container created via docker run...
• Get the logs of a pod - kubectl logs pods/container-name
  • Allows you to get the logs of a pod associated to a container created via docker run...
• Delete a pod - kubectl delete pods/container-name
  • Allows you to delete a pod associated to a container created via docker run...

Bi-directional service management is discussed in #81