[uss_qualifier] scd scenarios should confirm that entity deletion with a wrong OVN/version is impossible

[Shastick]

Description
The DSS has a missing OVN check in its OIR deletion endpoint, which the uss_qualifier currently does not detect. The same problem affects the CR deletion endpoint.

Request
This a kind of bug that we would want the qualifier to catch.

We should either create a new scenario, or extend an existing one, with a step that explicitly tries to delete an OIR with the wrong OVN.

Notes

We could easily add some steps to cover the same feature for Subscriptions and Constraint References, if their deletion with the proper version/OVN is not already covered

We should also verify that entity mutation with a wrong OVN is properly by scenarios.

Plan

• Subscription: add a test case to the SubscriptionSimple test scenario
• OIRs: there is no OIRSimple equivalent to the SubscriptionSimple scenario. We should probably create one.
• CRs: there is no CRSimple equivalent to the SubscriptionSimple scenario. We should probably create one.

Each of the scenarios above can also be enriched with an explicit test that will attempt mutating an entity. This is covered by #760.

Progress:

• OIRs: [uss_qualifier] add scd scenario checking that OIR deletion requires the correct OVN #761
• CRs: [uss_qualifier] add scd scenario checking that CR deletion requires the correct OVN #762
• Subscriptions: [uss_qualifier] simple SCD subscription scenario (DSS0005,5) #469
• Merge PRs on the DSS side
• [scd] oir deletion now checks for OVN correctness dss#1082
• [scd] cr deletion now checks for OVN correctness dss#1083
• Release fixed DSS
• Release monitoring image that includes [uss_qualifier] add scd scenario checking that OIR deletion requires the correct OVN #761 and [uss_qualifier] add scd scenario checking that CR deletion requires the correct OVN #762
• Update DSS qualifier config to match latest dss_probing configuration on the monitoring repo: [ci] prober/qualifer: update monitoring image to 0.9.0 dss#1123