Stabilizer task blocks due to gyro failure, freezing flight control

[gemenerik]

When the gyro sensor stops sending data unexpectedly, the stabilizer task can become blocked here. This causes all processes dependent on the stabilizer to freeze. The rate supervisor task does not appear to be designed to detect a complete block in the stabilizer task, nor does it take any corrective action beyond printing a warning.

This issue was observed on a Crazyflie at the office, where the gyro sensor tends to fail mid-flight, particularly under high thrust conditions. When this occurs, the Crazyflie gets stuck at high thrust. @tobbeanton confirmed the gyro failure by observing a complete absence of data interrupts using an oscilloscope.

Other parts of the system, like USB connectivity and cfclient plotting, continue to function normally.

Steps to Reproduce:

• Use a Crazyflie equipped with a gyro sensor that has a history of failing.
• Perform a flight with high thrust maneuvers.
• Observe if stabilizer-dependent tasks freeze when the gyro stops sending data.

Expected Behavior: The system should handle gyro sensor failures gracefully, preventing the stabilizer task from blocking and allowing dependent processes to cut the motors.

Actual Behavior: The stabilizer task blocks, causing all dependent processes to freeze, which can result in the Crazyflie being stuck at high thrust 🙈