using the CLI+KurtosisCloud should not rely on local Docker engine running

[leeederek]

Background & motivation

When I am using Kurtosis Cloud and manipulating it via the CLI, I have to have Docker running, otherwise I get an error like this:

➜  ~ clear
➜  ~ kurtosis context set cloud-58dbdc9d12424885a45aafc57444673b
INFO[2023-11-08T10:01:35-05:00] Switching context...
Error:  An error occurred running command 'set'
  Caused by: An error occurred stopping the local engine. The local engineneeds to be stopped before the context can be set. The engine status can be obtained runningkurtosis engine status and it can be stopped manually by running kurtosis engine stop.
  Caused by: An error occurred stopping engines using filters '&{GUIDs:map[] Statuses:map[RUNNING:true]}'
  Caused by: An error occurred stopping engines using filters: &{GUIDs:map[] Statuses:map[RUNNING:true]}
  Caused by: An error occurred getting engines matching filters '&{GUIDs:map[] Statuses:map[RUNNING:true]}'
  Caused by: An error occurred fetching engine containers using labels: map[com.kurtosistech.app-id:kurtosis com.kurtosistech.container-type:kurtosis-engine]
  Caused by: An error occurred getting containers with labels '{fields:map[label:map[com.kurtosistech.app-id=kurtosis:true com.kurtosistech.container-type=kurtosis-engine:true]]}'
  Caused by: An error occurred getting the docker containers with filter args '{fields:map[label:map[com.kurtosistech.app-id=kurtosis:true com.kurtosistech.container-type=kurtosis-engine:true]]}'
  Caused by: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Desired behaviour

I should not have to have the Docker engine running to switch contexts & to use the Cloud from my local machine (CLI).

How important is this to you?

Painful; the lack of this feature makes using Kurtosis frictionful.

What area of the product does this pertain to?

CLI: the Command Line Interface