Implement proper and centralized logging

MRs

• !214 (merged)

Description

By the time we start rolling out hardware to consumers, we need to have logging done in a way that, in case of a "Report issue", we can get as much useful information as possible in a structured way, that could be useful to everyone involved - kernel devs, plugin devs.

Scope

• Add log file rotation, keeping the logs per runs, up to a certain total file size per unit (already done in a previous ticket)
• Make the logs log directly to the file system, so that Docker cannot influence the log files or make them unavailable in any way shape or form
  • Add some kind of file/dir tagging based on the version used so that the files can easily be distinguishable between versions