core: ping: support device configuration options

### Current behaviour

Devices can be auto-detected, but configuration currently needs to be managed by whatever is connecting to and controlling them. That's fine for people using Ping Viewer, but is problematic if someone wants to do something like change the speed of sound of a ping1d sonar that they're forwarding MAVLink Distances from directly to their autopilot.

Issue raised after thinking about [this forum post](https://discuss.bluerobotics.com/t/using-ping-2d-without-ping-viewer/15376), which asked about how to do device initialisation for devices that aren't using Ping Viewer.

### Expected or desired behaviour

I think we should provide API support and UI elements for all the `set_*` messages from [ping-protocol](https://docs.bluerobotics.com/ping-protocol/), because then users can configure their sensors as desired as long as they're detected by the vehicle.

Longer term it would be cool if this kind of API could then be forwarded to Cockpit as part of some kind of standardised "widget configuration API" protocol, so it could auto-generate UI elements that allow configuring the connected device from a relevant Cockpit Widget.

### Prerequisites

- [X] I have checked to make sure that a similar request has not already been filed or fixed.