[uss_qualifier]Check and pass any additional fields in the InjectFlightRequest

[punamverma]

1. Check for any extra fields in InjectFlightRequest.
2. Populate additional_fields with those extra fields.
3. This will be used to pass modified behavior fields to mock_uss.
4. Eg. usage for modifying mock_uss behavior in a scenario-

  mod = MockUssFlightBehavior(
            modify_sharing_methods=["GET", "POST"],
            modify_fields={
                "reference": {"state": "Flying"},
                "details": {"priority": -1},
            },
        )
        
   mod_req = MockUSSInjectFlightRequest(
            operational_intent=req.operational_intent,
            flight_authorisation=req.flight_authorisation,
            behavior=mod,
        )
        
   plan_flight_intent(
             self,
             "Control_uss plans flight 2, sharing invalid operational intent data",
             self.control_uss,
             mod_req,
       )

[BenjaminPelletier]

Why would we want to change this deprecated class? To send a flight planning request to mock_uss including specification of bad behavior, we should use what MockUSSResource produces (a MockUSSClient) since control_uss is provided as a MockUSSResource in that linked test scenario. That's what I suggested here.

[punamverma]

Why would we want to change this deprecated class? To send a flight planning request to mock_uss including specification of bad behavior, we should use what MockUSSResource produces (a MockUSSClient) since control_uss is provided as a MockUSSResource in that linked test scenario. That's what I suggested here.

Will use it when I have MockUSSResource code ready. Just created this draft PR for Mike, if he wants to check how the mock behavior works. If you think its of no help, I ll remove the PR.