BUGFIX: some logs are done directly in the console / correct Logger startup sequence

[miroir-framework]

There is a problem with some files (e.g. RestClientStub) for which MiroirLoggerFactory.asyncCreateLogger never assigns the logger.

This yields the impossibility of searching / filtering certain logs, because they are put through the console and not properly tagged. The error does not seem to be linked to certain features of files, rather to some kind of famine happening, delaying the startup until the test is finished.

We should have a double handshake at global level, waiting for all loggers to be ready before doing any meaningful work.

To reproduce:

npm run testWithFullLog -w miroir-standalone-app -- DomainController.integ.Data

Then observe the log, they do not have the prefix added by the Logger:

RestClientStub params deploymentUuid 10ff36f2-50a3-48d8-b80f-e48e5d13af8e parentUuid undefined [...]

in opposition to other logs like:

##*-*-*## [22:45:49] info 3_miroir-core_CallUtils ### CallUtils callPersistenceAction called with action [...]