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

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

Start at the CLI entry point for `ops -update` and trace the check that reports a newer operator version. Reproduce the command with and without an active operator installation. Done means the update suggestion appears only when an active installation is detected.

Written by the indexing model from the issue text.