Zarf does not respect docker contexts about zarf HOT 1 OPEN

Thanks for the issue @mjnagel!

While, I'm not opposed to supporting this docker context's are more a feature of the CLI than the daemon. If we wanted to solve this we would have to get the url of the docker sock for that context.
To do this we can either:

• Figure out how to call the docker CLI from go using https://github.com/docker/cli. This can be trickier than it first seems, but if there is an easy way to get the host from calls to the cli package this would be best.
• Follow some of the docker logic summarized below to get the current context. Using the current context we would than have to look at the path ~/.docker/contexts/meta/33341cc9809c9410f1149a11fc4a79a53562069c7ff0c652fa18b8c83e3ec34b/meta.json and open that file to get the hostname of the docker sock

2. The "DOCKER_CONTEXT" environment variable.
3. The current context as configured through the in "currentContext"
field in the CLI configuration file ("~/.docker/config.json").

from zarf.