Improper invalid data incorrectly attributed to mock_uss provider

[BenjaminPelletier]

report.json is not attached because
An instance of this problem has not yet been observed at runtime -- rather, it can be deduced via inspection at design time.

Test check
Invalid data in Operational intent details shared by Mock USS for negative test check

Difference from expected behavior
This check is asserting that mock_uss (the control_uss resource in Data Validation of GET operational intents by USS test scenario) should have provided invalid operational intent data -- if mock_uss provides valid data, this check fails and the failure is attributed to the participant providing the mock_uss instance. However, mock_uss actually has no requirement to provide invalid data here -- instead, mock_uss's obligation is merely to respond with the data that the client (uss_qualifier) instructed it to respond with. If uss_qualifier or the test designer instructed mock_uss to respond with valid data, then the failure was caused by uss_qualifier or the test designer and not mock_uss. However, currently the failure will be incorrectly attributed to mock_uss instead.

The best way to disentangle the two responsibilities (providing invalid data, and sharing whatever data was specified) should be to change the expectation from expect_shared_with_invalid_data to expect_shared_with_specified_data (the actual requirement for mock_uss).

Additional context
This issue was raised in this thread but accepted as tech debt for #376.