Revamp Logging

A lot of what we've been doing over the past years was get it into a state where it can log data without impacting performance of the robot and be saved consistently. At FOPC we were able to accomplish both of these.

These are some ways to make logging more useful in future years.
- [x] Investigate/solve slow startup
- Partially resolved (see [logging-startup-performance](/FRC2706/2019-2706-Robot-code/tree/log-startup-performance))
- [x] Log periodic data separate from debug/trace data
- Save in machine readable file format (CSV?)
- [x] Capture `System.out/err` in debug logs
- [ ] Possibly way to combine DriverStation logging with other periodic logging

Review the logging-startup-performance branch referenced in the issue, then inspect the existing periodic, debug/trace, and DriverStation logging paths. Define how DriverStation logs should be combined with periodic logs and what consistent, machine-readable output should look like; the issue is done when that integration is specified and implemented without impacting robot startup or runtime performance.

Written by the indexing model from the issue text.