Update Debug info from received messages

## Summary
"\ specific data" in the Debug window should update to reflect the latest message data, instead of showing the current GUI settings.

## Additional information
- this is already the case for the Ping360's "Angle (grad)" and the Ping's "Distance (mm)" and "Confidence (%)", and the "Ping (#)", "Profile Frequency (Hz)", and most of the "Base data" section refer to data received from the device (so it's inconsistent to have it for some but not all)
- this would make the debug info more useful, by helping to identify any inconsistencies between what the GUI is requesting and what the device is actually doing/sending
- this would be useful in replays, for finding out the appropriate Ping360 "Range" to set, and more generally seeing what settings were used at the time of the initial recording (at the moment the Debug display is effectively useless in replay mode)
- brought up and discussed a bit in [this forum post](https://discuss.bluerobotics.com/t/pingviewer-replay-of-log-from-ping360-moos-app/10569)

Start by tracing where the Debug window displays the " specific data" and how received messages and GUI settings reach it. Compare the existing Ping360 and Ping data fields, then verify that all device-specific values show the latest received or replayed message data rather than current GUI settings.

Written by the indexing model from the issue text.