AP_SerialManager: add IBus Telemetry protocol param desc

[rmackay9]

PR #27695 added the feature but we forgot to add the parameter description

This change has been tested by running, "./Tools/autotest/autotest.py build.Copter test.Copter.Parameters" and reviewing the output of the "buildlogs/apm.pdef.xml" file.

<values>
          <value code="-1">None</value>
          <value code="35">ADSB</value>
          <value code="36">AHRS</value>
          <value code="40">AIS</value>
          <value code="34">AirSpeed</value>
          <value code="7">Alexmos Gimbal Serial</value>
          <value code="13">Beacon</value>
          <value code="41">CoDevESC</value>
          <value code="29">Crossfire VTX</value>
          <value code="45">DDS XRCE</value>
          <value code="33">DJI FPV</value>
          <value code="17">Devo Telemetry</value>
          <value code="42">DisplayPort</value>
          <value code="24">EFI Serial</value>
          <value code="16">ESC Telemetry</value>
          <value code="38">FETtecOneWire</value>
          <value code="10">FrSky SPort Passthrough (OpenTX)</value>
          <value code="3">Frsky D</value>
          <value code="4">Frsky SPort</value>
          <value code="5">GPS</value>
          <value code="30">Generator</value>
          <value code="8">Gimbal</value>
          <value code="27">HottTelem</value>
          <value code="49">IBus Telemetry</value>
          <value code="46">IMUDATA</value>
          <value code="44">IRC Tramp</value>
          <value code="25">LTM</value>
          <value code="11">Lidar360</value>
          <value code="43">MAVLink High Latency</value>
          <value code="1">MAVLink1</value>
          <value code="2">MAVLink2</value>
          <value code="32">MSP</value>
          <value code="20">NMEA Output</value>
          <value code="18">OpticalFlow</value>
          <value code="48">PPP</value>
          <value code="23">RCIN</value>
          <value code="9">Rangefinder</value>
          <value code="19">RobotisServo</value>
          <value code="26">RunCam</value>
          <value code="15">SBus servo out</value>
          <value code="22">SLCAN</value>
          <value code="28">Scripting</value>
          <value code="37">SmartAudio</value>
          <value code="39">Torqeedo</value>
          <value code="14">Volz servo out</value>
          <value code="31">Winch</value>
          <value code="21">WindVane</value>
        </values>

[rmackay9]

@nicole-ashley, if you get a moment, could you confirm you're happy with this? I called it "IBus Telemetry" but small changes in capitalisation etc are easy to add if you'd like it changed

[nicole-ashley]

Thank you for adding this. Ideally I would call it i-BUS Telemetry (note the lowercase i) as that's how it's styled in Flysky's documentation and marketing.

I know Flysky isn't the only company using i-BUS but they are the predominant one, and using this will make it match my updates to the wiki as well.

[rmackay9]

Hi @nicole-ashley,

i-BUS it is, thanks!

[rmackay9]

Thanks!