[uss_qualifier/scenarios/data_exchange_validation] Fix wrong check failure for lack of notification

[mickmis]

This addresses #797.
We keep track of the operational intent IDs that were created during the scenario run in order to ignore notifications about them that might have been sent asynchronously after the rejected planning attempt.
This also enhances the failure message of the check and add a low severity check for parsing the interaction query request.

[punamverma]

@mickmis Thanks for the fix. The changes look good to me. It would help solve the issue caused by async notification from the first test case being picked up by the next test case in the scenario.

Not for any action in this PR, but just as a discussion. Do you think it would be helpful to have a test that checks if a tested_uss sent a notification to the relevant USSes, about its ended operation? Would it cover any of the ASTM F3548 requirements?

[mickmis]

Not for any action in this PR, but just as a discussion. Do you think it would be helpful to have a test that checks if a tested_uss sent a notification to the relevant USSes, about its ended operation? Would it cover any of the ASTM F3548 requirements?

This could fall under SCD0090 depending on the interpretation of 'a managing USS [...] modifies an operational intent'.
Whether that interpretation is correct and whether such a test would be helpful are questions good to ask during the InterUSS weekly.