Re-implement session logging

[Koloss0]

🗒️ Task Description

Summary
The old version of SOTI (before Urwid) used to support session logging. This meant that each time the program was run, a new YAML file would be created that stores a history of all the commands sent to and from the CAN bus. This functionality was removed during the Urwid refactor so this issue is about re-implementing it.

Details
Session logging should begin once the user selects an input device and the main screen is booted up. Implement this in a way that doesn't complicate the core logic too much.

✅ Completion Criteria

• Sent and received messages can be seen in session log files under /save-data/sessions/
• The format is similar to the old implementation. Mild re-touching is permitted if you have ideas!

📂 Affected Components

• Affected Files:
  • main_screen.py: You may have to change this
  • session_logger.py: This is where the meat of the code should be

🚧 Notes / Reference

• Please refer to the old implementation of the session logger to get an idea of how it should work (see here). You should run it and see the format of the YAML files that get generated.