Improve Scenarioo Reporter

[bruderol]

Some findings from junit5 refactoring to be addressed in both versions (junit4 and junit5) of the example:

1. Exception information (stacktrace) should be attached to scenarioo report on test failure.

2. WebDriver is initialized to listen for all interactions for each use case - shouldnt the listener only start to report during test execution (such that a test could do some test preparation without reporting it?)? Currenty it looks a bit weird this initialization is only done once per test class. In junit5 there is a special hook for BeforeTestExecution that could be used for that.

   • also this kind of opening the browser for each use case leads to browser poping always up again during test execution on desktop for many tests (maybe we should reuse the browser somehow)

3. ScenariooEventListener: better rename to ScenariooStepReporter or even WebDriverStepReporter?

4. UseCaseContext:

   • I think we should rename this to "ScenriooReporterContext" or something similar, since it holds more than just the use case
   • Ideas for junit5 only:
     • maybe it would be better to not handle that as a Singleton through the context holder but directly hold it inside the reporter ??
     • also we should later change it to use more of the JUnit 5 context info - see class ExtensionContext (e.g. DisplayName!)

5. Further Ideas for Junit 5 only:

   • support Tag annotation from junit5