[mock_uss] Add user notifications for missing fields in injected flights

[the-glu]

Follow #910

Tested, I added a filter + a new raw_telemetry field for internal purpose, because everything was crashing with bad telemetry data ^^'

[Shastick]

Sounds like a wise thing to do :)

[mickmis]

This is going to trigger a notification for every single missing field in any telemetry point. That's not realistic since we'd want that only if there are missing fields for a while, but that could be acceptable behavior for the mock USS.
However what it is not covering is the lack of any telemetry point for a while. Which we will need for NET0400. Could you add that? Thanks!

[the-glu]

Which we will need for NET0400. Could you add that? Thanks!

We planned with @Shastick to implement that one in a different PR, this is only for NET0030 on purpose :)

This is going to trigger a notification for every single missing field in any telemetry point. That's not realistic since we'd want that only if there are missing fields for a while, but that could be acceptable behavior for the mock USS.

For the mock uss we probably want that for testing: It's reporting all missing fields with location on purpose if debugging is needed (and that shouldn't add much overhead, when testing we do only set one missing field in one telemetry). Also I'm not sure, but complaining immediately is not an issue based on the standard no?

[Shastick]

Yep, I don't see a reason to limit ourselves to a single notification, and the current approach makes the logic very simple.

The intention for the scenario is to assume that we have at least one notification sent (ie, the notification count over the period is non-zero, and/or the total number of notifications at the end of the scenario is higher than when it started.