Draft: chore: Assert vulnerability count equality in report_shared_examples.rb
What does this MR do?
Previously, the include_json assertion might not make
the outcome very clear if there is an ordering issue. If
we also assert on the count it can be clear whether the report content
is a different order or missing results
For example, this job failure required manual debugging to determine whether the order had changed or the data itself