[CLI] operator update should be suggested only if an installation is detected

[francescotimperi]

Updating the ops cli using 'ops -update` always reports that a newer version of the operator is available and that it can be updated using a specific tasks, e.g.

`Welcome to ops! Setting up...
Cloning tasks...
Enumerating objects: 3661, done.
Counting objects: 100% (289/289), done.
Compressing objects: 100% (110/110), done.
Total 3661 (delta 164), reused 271 (delta 158), pack-reused 3372
Tasks downloaded successfully

New operator version detected!
Current deployed operator can be updated with: ops update operator`

We should change the behaviour to trigger this check only if an active installation is detected

[sciabarracom]

I have no idea how to fix this so I am reassigning...

[d4rkstar]

@francescotimperi can we use the ops setup status result and trigger the check if it is different from nothing installed yet ?

[francescotimperi]

@francescotimperi can we use the ops setup status result and trigger the check if it is different from nothing installed yet ?

This could work, but there's the need to ensure that the ops setup status commands, returns nothing installed yet even when there's no docker available. I tried on a MAC, with not docker running and the ops setup status command failed...due to something like

franz@MacMini-di-Francesco ~ % ops setup status
ERROR: failed to list clusters: command "docker ps -a --filter label=io.x-k8s.kind.cluster --format '{{.Label "io.x-k8s.kind.cluster"}}'" failed with error: exit status 1
Command Output: Cannot connect to the Docker daemon at unix:///Users/franz/.docker/run/docker.sock. Is the docker daemon running?
Cluster Apache OpenServerless not found

In my opinion, this control about the operator version should happen only if there's an active installation available, by using for instance the result of the ops debug operator:version. This should return a non empty value matching the currently installed operator version, if any.