[uss_qualifier] Improve test run report validation

[BenjaminPelletier]

Currently, all checks in all dev tests (used for CI) pass. This limits test coverage substantially as no logic involving failed checks is ever exercised. This PR reworks test run report validation to allow for more sophisticated test run validation criteria, including allowing (and requiring) the test runs of some configurations to contain failed checks (and, in the future, additional and more specific characteristics).

[barroco]

Please note the comment inline

[barroco]

I may have misunderstood but if we assume that Critical is bigger than Low severity, then it looks like the operator implementation is not completely correct.

self	other	expected gt	implemented gt	expected == implemented ?
Critical	Critical	False	False	✅
Critical	High	True	False	?
Critical	Medium	True	False	?
Critical	Low	True	False	?
High	Critical	False	True	?
High	High	False	False	✅
High	Medium	True	False	?
High	Low	True	False	?
Medium	Critical	False	False	✅
Medium	High	False	False	✅
Medium	Medium	False	False	✅
Medium	Low	True	True	✅
Low	*	False	True	?

[BenjaminPelletier]

🤦 thanks. Ok, fix verified with:

from monitoring.uss_qualifier.common_data_definitions import Severity

severities = (Severity.Critical, Severity.High, Severity.Medium, Severity.Low)
operators = ("==", "!=", ">", ">=", "<", "<=")

for op in operators:
    corner = f"↓ {op} →"
    print(f"{corner:<10}" + "".join(f"{s.value:<10}" for s in severities))
    for r in severities:
        line = f"{r.value:<10}"
        for c in severities:
            v = eval(f"r {op} c")
            line += f"{v:<10}"
        print(line)
    print()