#155 add tests for report logging

[Lysoun]

This PR extends the existing unit tests for the Report class. Resolves Add tests for report logging #155

Code mainly done by @frankschmitt, I just rebased their PR on dev

[github-actions[bot]]

Unit Test Results

  53 files  ±0    53 suites  ±0   59s :stopwatch: -11s 195 tests +8  194 :heavy_check_mark: +8  1 :zzz: ±0  0 :x: ±0 

Results for commit 199eafdb. ± Comparison against base commit 9b704d7f.

This pull request removes 3 and adds 11 tests. Note that renamed tests count towards both.

``` datamaintain.core.report.ReportTest$ExecuteLogs ‑ should not display relative paths when porcelain name is null() datamaintain.core.step.check.CheckerTest ‑ should failed when check rule name doesn't exist() datamaintain.core.step.check.CheckerTest ‑ should failed without launching any rule when a check rule name doesn't exist() ``` ``` datamaintain.core.report.ReportTest$ExecuteLogs ‑ should not display relative paths when porcelain is false() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print details if verbose is set() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only summary if neither verbose nor porcelain are set() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only up to CHECK step if configured() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only up to EXECUTE step if configured() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only up to FILTER step if configured() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only up to PRUNE step if configured() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only up to SCAN step if configured() datamaintain.core.report.ReportTest$ExecuteLogs ‑ should print only up to SORT step if configured() datamaintain.core.step.check.CheckerTest ‑ should failed when check rule name doesn't exist() … ```