[monitorlib/rid injection] Enforce and fix UAS ID at TestFlight level

[the-glu]

This PR partially addresses #1003 by fixing the UAS ID Field duplication in the TestFlight class, meaning it will be fixed when injecting a flight and when getting data from an injected flight.

A small typo has been fixed in checks, and a side small fix of filter_invalid_telemetry passed to the parent class has been done.

[the-glu]

Remark:

It will also mean mock_uss will clean those field

[mickmis]

So if the TestFlight is invalid with this change the constructor will start raising ValueError. That sounds reasonable in isolation however is this caught and handled correctly in callers?
When injecting a flight or getting data from an injected flight that sounds reasonable since that would be a configuration error.
However within the mock USS, or potentially other callers, this may not be appropriate. E.g. in mock USS for such an issue I would expect the mock USS to catch the exception and return an HTTP bad param response.
Have you checked those things?

Other than that the change LGTM.

[the-glu]

So if the TestFlight is invalid with this change the constructor will start raising ValueError. That sounds reasonable in isolation however is this caught and handled correctly in callers? When injecting a flight or getting data from an injected flight that sounds reasonable since that would be a configuration error. However within the mock USS, or potentially other callers, this may not be appropriate. E.g. in mock USS for such an issue I would expect the mock USS to catch the exception and return an HTTP bad param response. Have you checked those things?

Seems mock USS handle it already and return the response:

TestFlight doesn't seems to be used in others situation, so I do assume we're fine?

[mickmis]

Thanks for checking 👍