Switch to mavlink-router tlog files

[clydemcqueen]

The tlog (MAVLink) files generated by mavlink-router have a few neat properties:

• they start / stop when the autopilot starts / stops, so there is a 1:1 correspondence between BIN files and tlog files
• they are written even if QGC has crashed, the Windows network bridge is borked, etc.
• we can collect tlog and BIN files at the same time, simplifying post-dive ops

I've looked a few of these tlog files, and they seem to be at least as good as the QGC-generated files. We are missing some DISTANCE_SENSOR messages in both, see https://github.com/bluerobotics/BlueOS-Water-Linked-DVL/issues/44

The only complication is that BlueOS might switch to a different MAVLink routing solution.

I think we should collect these after every dive.

Actions:

• [ ] update the pipeline doc
• [ ] use these as input to the 1-Hz telemetry generator