[FEATURE]: make the fatal handler tell us the fatal before it borks out

[ineskhou]

Problem Description

When we fail tests currently, we bork before we get the fatal events. We can still see the events in the serial connections, but it would be useful for debuging to have it be a part of the event stack

Proposed Solution

make the fatal handler tell us the fatal before it borks out

Impact Assessment

those who love debuggers

Priority

[LeStarch]

@ineskhou @Mikefly123 I figured out the issue. It is the dreaded "@LeStarch doesn't understand microsecond/millisecond/second conversions" bug.

If I bump it to 1 second proper, this is likely enough time for data to get out the UART and to disk. However, it won't escape the beaconing/lora time window....which will almost always drop the event. Thoughts?

[LeStarch]

The one second fix is in #140

[Mikefly123]

I think if the Fatal message can get to the file system and can be read later then that works good enough for this mission!

Not being able to read a fatal in real time via the radio is not ideal, but I think the use case for that is narrow enough (something goes wrong during a ground station pass) that you can hope the operators will already have enough data to reconstruct what went wrong without the explicit message