Finalize `watch` command and documentation

[lbroudoux]

Reason/Context

We need to progress on the next version of CLI and improve some stuff regarding the watcher behavior.
The primary goal is to be able to launch the watcher from the command line, using the same binary.

Description

I checked the import command and saw there's already a --watch flag. At first, I thought it was the right place to launch the watcher but I saw that this just updates the watcher configuration file.

I wonder:

1. Should we keep that this way and have another command like microcks watch that starts the watcher in the foreground until we Ctrl+C it ?
2. Should we just launch the watcher on presence of this flag in the microcks import command (here again, waiting for the Ctrl+C signal)

Also, I saw that each entry in the watcher configuration file has a list of contexts attached. Launching the watcher externally (as a separate command) means that without context, the watcher cannot find the correct Microcks instance to push local changes to...

Maybe then: we should be able to handle both case? Launching the watcher with the import - in that case, it reuses the current context + launching the watcher independently - in that case, it uses the context configured in the wath config file.

What do you think @Harsh4902?

Implementation ideas

No response

[Harsh4902]

@lbroudoux Totally agree. Give me some time, I'll come back with the solution. Currently, I'm a bit occupied.

[Caesarsage]

i think we can go with the hybrid approach where the import --watch run the actual watcher as its more user intuitive and we can also have another standalone command @lbroudoux @Harsh4902