Discovery process should re-watch the network config map if provider list changes

[fracappa]

Hi folks.

I want to highlight a potential missing behavior on the FLUIDOS Node architecture.

More specifically, the discovery process can now return an empty list when no provider can fulfill the consumer requests.

However, if a fulfilling provider comes out afterwards, there is no way of using it in the current implementation.

Moreover, the lifetime of a Discovery CR (which keeps a Discovery process alive) should be a temporary resource which can be cleaned once the linked Solver CR expires.

So my proposal is to integrate the following features:

• Watching logic on the Discover controller, which triggers the discovery process if it is still running and a new provider comes out.
• Delete the Discovery CR (and so killing the Discovery process) once the linked Solver CR expires.

Please, give any feedback you might have.

Thanks,
Francesco