Added fields to the MavlinkReciever::handle_message_distance_sensor() method

[mcsauder]

Describe problem solved by the proposed pull request
This PR addresses Issue #11133. The PR adds missing fields and a TODO to indicate why the missing field cannot be populated due to the mavlink message definition lacking that field.

At some point we will need to get the mavlink definition updated to match as well, but at least for now there will be a placeholder reminder.

Additional context
See Issue #11133
Please let me know if you have any concerns on this PR. Thanks!

-Mark

[TSC21]

@mcsauder the only field that is missing is the signal quality: https://mavlink.io/en/messages/common.html#DISTANCE_SENSOR. For the signal quality, one can always set it to max so to be accepted.

[mcsauder]

@mcsauder the only field that is missing is https://mavlink.io/en/messages/common.html#DISTANCE_SENSOR. For the signal quality, one can always set it to max so to be accepted.

Thanks @TSC21 ! I've updated the commit to fix things up. I was blind! Thanks again!

[TSC21]

@mcsauder the only field that is missing is https://mavlink.io/en/messages/common.html#DISTANCE_SENSOR. For the signal quality, one can always set it to max so to be accepted.

Thanks @TSC21 ! I've updated the commit to fix things up. I was blind! Thanks again!

No problem.

[mcsauder]

Hi @TSC21 , I added a default value for the signal quality that mirrors the values being set in distance sensor drivers lacking that value as well as the default PX4Rangefinder value. Thanks for your feedback!

[mcsauder]

Thanks @TSC21 !