Reset max stress level metric to minimum

[vmzhivetyev]

Current Behavior

The Demag_Detected_Metric_Max currently stores the maximum value observed since the ESC was armed. This results in the metric becoming static after reaching its peak, never decreasing until the ESC is disarmed.

Proposed Change

Reset the Demag_Detected_Metric_Max metric each time a STATUS telemetry packet is sent. So that the value in a STATUS telemetry packet would represent the Max stress level in the last second (according to current scheduler implementation).

Rationale

• Offload the logic of processing the max stress level to the FC (e.g., Betaflight), allowing for more sophisticated and/or different modes of analysis.
• FC side alarms will be able to activate only when stress is genuinely high, rather than remaining permanently active after the threshold is exceeded.
• Make the behavior consistent with Demag/Desync/Stall flags, which are also part of the STATUS EDT packet.
• Speaking of blackbox logs, such change would provide meaningful data throughout the entire flight, instead of only capturing information before the first high-stress situation like a snap roll.

Tests

This is what 40 seconds of blackbox log look like if recorded with this change.

[github-actions]

Build artifacts:

• Download bluejay-ci-219 (Expires on 2024-10-12)

[stylesuxx]

Thank you for the comprehensive PR, makes sense in regards to making the behavior consistent.

I think it'd be important to adjust the EDT specs accordingly, since it's not specified in which timeframe context this status frame value is to be seen.

Ping @AlkaMotors - how do you handle the max stress level in the EDT status frame in AM32 - AFAIK you have that implemented too, no?

[github-actions]

Build artifacts:

• Download bluejay-ci-220 (Expires on 2024-10-13)

[hyp0dermik-code]

LGTM