Add better logging for production

[ewc340]

Many problems we have seen in production (i.e. connection issues etc) are hard to debug because we don't have clear logs in the code, we should add logging for crucial parts in the code and save them to a file. We can also add a log view somewhere in Dawn so the logs can be easily accessible.

We may have to do some log sanitation for existing logs since current logs are pretty noisy and repetitive. (Related issue: #65)

[benliao1]

To prevent another situation like what happened in the last match in spring comp 2021 (we couldn't figure out what time a robot failed), it would be great if Dawn saved a copy of the logs it received from the robot locally somewhere in the application data and maybe deleted the logs once every week or once a day or something so that the file doesn't get too big. Currently, the behavior is simply to print out all logs received from the robot into the console window only if it's open; and if the console window is closed, all received logs are lost to the ether even after re-opening the console window.

Additionally, we could have a menu option (like perhaps Debug -> View Robot Logs) that allows students to access both the logs sent to the robot over the past day or week that are stored on the student's machine (which are log level INFO and above) as well as the logs stored on the robot for all time (which are log level WARN and above). The robot logs are stored on the Raspberry Pi at /home/pi/runtime/logger/runtime.log, so to get the information, just scp the file off of the robot and display it in a new window, similar to the way the "Download Code From Robot" button currently works.