- SYS_FMU_TASK is now enabled for PX4FMU_V4 PX4FMU_V4PRO PX4FMU_V5, but
  it's only set on autoconf
- v5 companion is now TELEM2 (same as all other boards)

useful in case the ekf replay topics are not enabled

This is required for generating documentation

This allows to build all params and test them.

This hides these parameters by default from the user.

This helps with param transfers and will hide these params by default from the user.

This makes it easier for QGC to parse.

This allows to mark parameters as volatile.

No functional change, but this avoids numerical issues in the check routine. Since the routine will tend to false positives, we will tend to send more param updates than required in case of numerical noise of the float representation. This is desired, as we prefer to send two updates rather than not sending one.

Volatile parameters are ones that do not represent a fundamental configuration change but rather than incrementally changing settings. These include logged flight hours or sensor offsets. Marking them as volatile avoids these parameters forcing time-consuming telemetry updates.

Parameters can change not just based on GCS request, but also due to internal code or requests by a different valid connected control authority such a cloud service. This change ensures that all connected systems get updated via MAVLink asynchronously.

All param handling happens in the param manager.

Pure comment edit

This helps subscribers to understand if they should update their parameters or not. We will extend this with other flags such as the current save status and alike.

This should help keeping the GCS up to date about asynchronous changes on the autopilot.

This marks the learned bias parameters as volatile (as they change in flight without external configuration) and marks them as system level, which should hide them by default from the UI