Better logging #22
Description
Considering that how the new framework design is going, quite a bunch of things will happen under the hood during an Inversion: directives will be called, stopping criteria evaluated and possible updated and initialized.
It might be a good idea to have a common logger accessible to all code where we can store information (and optionally warning) messages without cluttering the stdout and stderr. They wouldn't need to be fancy prompt output (like rich), just a builtin logger should be enough.
The repo already has one, that is currently used to show the information message once an inversion finished. Maybe it would be nice to use the same one and store other information messages with DEBUG level.