Adds loggers to report flow

[madelondohmen]

Changes

This PR adds some loggers to the report flow.
Event codes can be found here: #3043 (comment)

Issue link

Closes ...

QA notes

Please add some information for QA on how to test the newly created code.

---

Code Checklist

• All the commits in this PR are properly PGP-signed and verified.
• This PR only contains functionality relevant to the issue.
• I have written unit tests for the changes or fixes I made.
• I have checked the documentation and made changes where necessary.
• I have performed a self-review of my code and refactored it to the best of my abilities.

• Tickets have been created for newly discovered issues.
• For any non-trivial functionality, I have added integration and/or end-to-end tests.
• I have informed others of any required .env changes files if required and changed the .env-dist accordingly.
• I have included comments in the code to elaborate on what is not self-evident from the code itself, including references to issues and discussions online, or implicit behavior of an interface.

---

Checklist for code reviewers:

Copy-paste the checklist from the docs/source/templates folder into your comment.

---

Checklist for QA:

Copy-paste the checklist from the docs/source/templates folder into your comment.

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
75.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ammar92]

I suggest looking at the code base on how we currently deal with the logs and event codes. See for example the constants defined in octopoes/octopoes/types.py, similar constants can be defined in rocky/reports/views/mixins.py and rocky/rocky/scheduler.py. Also note that event codes are currently implemented as integers, so prefixing with 0 and sending them out as strings is wrong. For example and in the style of the already existing logs, "080071" would be something like 800071