[TT-1140] Universal log processor + modified log verifier

[Tofel]

Why?

So that we can use CL node log verification that was added for k8s also in docker!

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes in this pull request are aimed at enhancing the logging and log processing capabilities of the system. By introducing a new log processor, refining the log scanning and verification process, and enabling more granular control over log messages, these changes strive to improve the system's ability to analyze and manage log data more effectively.

What

• logstream/logprocessor.go
  • Added a new file introducing LogProcessor struct and methods for processing container logs and creating a processor for regex matching. This allows for more sophisticated log processing based on the content of the logs.
• logstream/logstream.go
  • Added a new method GetLogLocation to retrieve log locations, enhancing the system's capacity to manage and reference log files.
• testreporters/reporter_model.go
  • Modified WriteTeardownLogs to utilize a new method FindAllLogFilesToScan with an additional parameter, allowing for more precise log file scanning.
  • Introduced FindAllLogFilesToScan as a replacement for findAllLogFilesToScan, now accepting a partialFilename parameter to filter log files more effectively.
  • Replaced allowedLogMessage with AllowedLogMessage struct and added a new function NewAllowedLogMessage, providing a more flexible way to define and handle allowed log messages.
  • Changed verifyLogFile to VerifyLogFile and added parameters for failure threshold and allowed messages, offering a more customizable approach to log verification.

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube