Implement tests for F3548 DSS requirements

[BenjaminPelletier]

Is your feature request related to a problem? Please describe.
uss_qualifier should aim to verify as many requirements from ASTM F3548-21 as practical. We currently test many of the requirements, but there are still currently-untested requirements that are feasible to test as well. This issue covers DSS requirements, similar to #274 which covers non-DSS requirements.

Describe the solution you'd like
Add tests to the F3548-21 test suite which verify compliance to the following F3548-21 requirements. The list below is intended to reflect the current status and should be updated when new tests are written. The list should be in rough priority order after considering the value of verifying the requirement and the difficulty of implementation.

• DSS0005,5 [uss_qualifier] simple SCD subscription scenario (DSS0005,5) #469
• DSS0015 [uss_qualifier] scd dss0015 ensure max subscription duration is enforced #475
• DSS0100,1
• DSS0210,1
  • a, c, e, f, g, h, i: [qualifier] DSS0210,1 – add initial inter-DSS subscription synchronization scenario #512
  • b DSS0210,1b – check that replicated SCD subscriptions retain their manager (standalone) #548
  • d [uss_qualifier] DSS0210,1d – check that DSS properly propagates a subscription's area #538
• DSS0210,2
  • OIR: a, b, c, d, f [uss_qualifier/scenarios/utm/dss/OIRSynchronization] DSS0210,2a-b-c-d-f: check OIR deletion propagation #573
  • OIR e [uss_qualifier/scenarios/utm/dss/OIRSynchronization] DSS0210,2e: check OIR area propagation #549
  • Constraints: [uss_qualifier] constraint reference sync: cover deletion 5/5 #708
• DSS0210,A2-7-2,7
  • Subscriptions [qualifier] DSS0210,A2-7-2,7 validate authentication for subscription CRUD+search endpoints #514
  • Operational Intents [qualifier] DSS0210,A2-7-2,7 validate authentication for OIR CRUD+search endpoints #546
  • Constraints [uss_qualifier] expand the authentication validation scenario to include constraint reference endpoints #690
  • Availability States [uss_qualifier] scd endpoint auth validation: cover uss availability #710
• DSS0210,A2-7-2,1a implicitly covered by DSS0210,2
• DSS0210,A2-7-2,1b implicitly covered by DSS0210,2
• DSS0210,A2-7-2,2 DSS0210,A2-7-2,2(a|b) create/update Op. Intent Ref. requires correct OVNs in keys (standalone) #539
  • a, b
• DSS0210,A2-7-2,3a DSS0210,A2-7-2,3,a Op. Intent Ref. can be deleted from any instance of a DSS deployment #540
• DSS0210,A2-7-2,4 Entity <-> Subscriptions interactions
  • Subs cleaned up after expiry
    • should subs auto-delete? See this question. Not currently, it's fine to check that expired subs don't trigger notifications
    • No more interaction after expiry
  • Subs can be created/deleted on any DSS [qualifier] DSS0210,1 – add initial inter-DSS subscription synchronization scenario #512
  • OIRs DSS0210,A2-7-2,4 subscription-OIR interactions over multiple DSSes (subscription creation & update) (standalone) #541
  • Constraints (TODO)
• DSS0210,A2-7-2,5 (standalone) subscription interactions over multiple DSSes when sub is deleted
  • OIRs DSS0210,A2-7-2,5a subscription-OIR interactions over multiple DSSes (subscription deletion) (standalone) #542
  • Constraints (TODO)
• DSS0020 – access any DSS obtain same result
  • Subscriptions
    • Read [uss_qualifier] check off DSS0215 and DSS020 for subscriptions (partial) #533
    • Write DSS0020 – SCD subscriptions can be updated or deleted from any DSS in a deployment (standalone) #547
  • Operational Intents
    • Read implicitly covered by DSS0210,2 [uss_qualifier] reference DSS0215 and DSS0020 (DAR sync & DSS consistency) in OIR sync documentation #688
    • Write/Delete implicitly covered by DSS0210,2 [uss_qualifier] reference DSS0215 and DSS0020 (DAR sync & DSS consistency) in OIR sync documentation #688
  • Constraints [uss_qualifier] constraint reference sync: cover deletion 5/5 #708
  • Availability States [uss_qualifier] new SCD scenario to check synchronization of USS availability states #691
• DSS0215 return after DAR is updated
  • Subscriptions
    • Create [uss_qualifier] check off DSS0215 and DSS020 for subscriptions (partial) #533
    • Mutate/Delete [uss_qualifier] (doc only) cover dss0215 and dss0020 for deletions/mutations in the subscription sync scenario #565
  • Operational Intents
    • Create implicitly covered by DSS0210,2 [uss_qualifier] reference DSS0215 and DSS0020 (DAR sync & DSS consistency) in OIR sync documentation #688
    • Mutate/Delete implicitly covered by DSS0210,2 [uss_qualifier] reference DSS0215 and DSS0020 (DAR sync & DSS consistency) in OIR sync documentation #688
  • Constraints [uss_qualifier] constraint reference sync: cover deletion 5/5 #708
  • Availability States [uss_qualifier] new SCD scenario to check synchronization of USS availability states #691
• DSS0100,2 [uss_qualifier/utm] Add make_report test step fragment #552
• DSS0200 [uss_qualifier/scenarios/dss] Add CockroachDBAccess test scenarios #513
• DSS0205 [uss_qualifier/scenarios/dss] Add CockroachDBAccess test scenarios #513
  -- MVP line --
• DSS0210,A2-7-2,1e [uss_qualifier] constraint reference sync: cover deletion 5/5 #708
• DSS0210,A2-7-2,1f [uss_qualifier] constraint reference sync: cover deletion 5/5 #708
• DSS0210,3 [uss_qualifier] new SCD scenario to check synchronization of USS availability states #691
• DSS0005,3 [uss_qualifier] constraint reference sync: cover deletion 5/5 #708
• DSS0005,4 DSS should implement queryConstraintRefs -> update scenarios from [uss_qualifier] constraint reference sync: cover deletion 5/5 #708 once merged
• DSS0210,A2-7-2,6 [uss_qualifier] new SCD scenario to check synchronization of USS availability states #691
• DSS0210,A2-7-2,1e show that queryConstraintRefs returns what was written from any DSS (add to CR sync scenario)
• DSS0210,A2-7-2,1f show that getConstraintReference returns what was written from any DSS (add to CR sync scenario)
• DSS0210,A2-7-2,3c entity reference can be deleted and all DSSes will correctly not show it in queryConstraintReferences
• DSS0210,A2-7-2,3d entity reference can be deleted and all DSSes will correctly not show it in getConstraintReference

Additional context
If discussion about how to construct a test or tests for any of the requirements above, a separate issue should be created for the implementation of those tests (rather than adding a comment on this issue).