Add some logging for the queues

[frode-aarstad]

Issue
Resolves #9618

When running everest with the --debug flag we now provide logs from websockets with sizes of the events:

2025-03-20 08:37:53,241 websockets.client DEBUG: < TEXT '{"batch":4,"event_type":"EverestBatchResultEven...e_names":["distance"]}}' [2342 bytes]
2025-03-20 08:37:53,342 websockets.client DEBUG: < TEXT '{"batch":5,"event_type":"EverestStatusEvent","e..._OPTIMIZER_EVALUATION"}' [90 bytes]

Also added a test for logging from plugins

(Screenshot of new behavior in GUI if applicable)

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'just rapid-tests')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codspeed-hq]

CodSpeed Performance Report

Merging #10396 will not alter performance

_{Comparing frode-aarstad:add-logging-for-queues (2fb3705) with main (b5b4abf)}

Summary

✅ 25 untouched benchmarks

[DanSava]

Looks good 👍

I assume it was not possible to split the changes in two commits to reflect the two issues you are closing. One related to logging and one related to handling connection errors

Also some conflicts need to resolved before merging.

[frode-aarstad]

Looks good 👍

I assume it was not possible to split the changes in two commits to reflect the two issues you are closing. One related to logging and one related to handling connection errors

Also some conflicts need to resolved before merging.

I removed the issue with the websocket handeling as its not fixed and put it back in todo