Satellite: send latest status with extrasystoles

This is an attempt to fix #204 (closed), however, status messages are not reset currently which means following the MissionControl tutorial will generate the status from the failed init attempt:

But the very same status will be reported over and over again, even when reconfiguring with a proper config and starting a run. This issue also exists currently already in get_status.

I guess this can only be properly solved with implementing #96 (closed) ?

For now I resolved this by resetting the status string whenever there was a successful transition - unless these were failure, interrupt otherwise we overwrite the error immediately again. There of course still is sort of a "data race" between the transition messages going out, but I think this is more of a cosmetic issue. What do you think?

This fixes #204 (closed)