Fix JSON line logging

[ammar92]

Changes

This implementation updates the default logging format to support both text and JSON line logging. It also fixes the double-formatted JSON logging issue in Rocky caused by a misconfiguration. Additionally, a few event codes have been added for the Octopoes API connector.

Issue link

(Partially) closes #3397

Demo

QA notes

Set the following environment keys:

SCHEDULER_LOGGING_FORMAT=json
BOEFJES_LOGGING_FORMAT=json
BYTES_LOGGING_FORMAT=json
OCTOPOES_LOGGING_FORMAT=json
LOGGING_FORMAT=json

The services should produce JSON logs generated by OpenKAT in the following format:

{"event": ..., "level": ..., ...}

---

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.

[underdarknl]

Lets add this to the Docs.

[underdarknl]

I've added these to
#3043