Lazy load logger in ResultUtils to supress SLF4J warings in AnnotationProcessing

[rPraml]

Context

The JavaDocDescriptionsProcessor requires the ResultsUtils.generateMethodSignatureHash
When the ResultsUtils class is loaded during AnnotationProcessing, it has initialized also the SLF4J framework, which leads to some SLF4J warnings while compiling.

Getting the logger only, when it is really needed will solve the issue (in theoretical more costs in performance, but this does not matter here)

See #962 for more info

Checklist

• Sign Allure CLA
• [!] Provide unit tests - this is difficult to unit test as it happens only, if there is no SLF4J implementation present - I've verified it manually and the warning is gone in my project with this change (maybe give me a hint how to test it)

[rPraml]

@baev maybe you can provide feedback to this change

[baev]

fixed via #981

[baev]

Thanks for the contribution!