Persist TRACE logs on test error

The challenge is that we don't know if we'll need the TRACE log before running the test while keeping all traces from all tests takes a lot of disk space and consumes IO resources.
=> First, set logs level at WARN only.

Then, add a new feature in the test framework called "Just In Time log interceptor" will be installed in front of Log4J and register itself to Java logging.
It will consume to application logs, transmitting them to a disruptor.
The disruptor will consume and reify the log messages in an off-heap map to avoid any overhead.
At the end of a test, the framework will inform the JIT log interceptor how to flush the logs: either to simply drop them or to persist them (at TRACE level), in case of test error, for analysis.

The target NXP version is the current dev (7.2). Other versions may benefit of an alternative implementation; in all cases, the TRACE logs are deactivated in all versions.