Example of a custom visual (logged) static debugger

This is created in relation to the test hackathon.

The purpose is to demonstrate the usage/attachment of a custom static visual debugger on junit5 component tests.

This could be helpful when there is a test failure,  to compare the execution path traces with a successful run for example.

Information about static fields used could be provided, in order to help with further investigation with intermittent faults for example.

It could be applicable to all components.