Collapse mode should print number of matches #144
Description
Currently, collapse mode output looks something like (i.e.: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/periodic-ci-openshift-eng-ocp-qe-perfscale-ci-main-aws-4.18-nightly-x86-payload-control-plane-6nodes/1937828910855098368/artifacts/payload-control-plane-6nodes/openshift-qe-orion-node-density/build-log.txt):
2025-06-25 13:16:52,807 - Orion - INFO - file: orion.py - line: 125 - 🏹 Starting Orion in command-line mode
2025-06-25 13:16:52,820 - Orion - INFO - file: utils.py - line: 241 - The test payload-node-density has started
2025-06-25 13:16:52,821 - Matcher - INFO - file: matcher.py - line: 65 - Executing query against index=perf_scale_ci-*
2025-06-25 13:16:52,922 - Orion - INFO - file: utils.py - line: 52 - Collecting podReadyLatency
2025-06-25 13:16:52,923 - Matcher - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-06-25 13:16:52,964 - Orion - INFO - file: utils.py - line: 52 - Collecting apiserverCPU
2025-06-25 13:16:52,964 - Matcher - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-06-25 13:16:54,053 - Orion - INFO - file: utils.py - line: 52 - Collecting ovnCPU
2025-06-25 13:16:54,054 - Matcher - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-06-25 13:16:56,835 - Orion - INFO - file: utils.py - line: 52 - Collecting etcdCPU
2025-06-25 13:16:56,835 - Matcher - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-06-25 13:16:57,659 - Orion - INFO - file: utils.py - line: 52 - Collecting kubelet
2025-06-25 13:16:57,660 - Matcher - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
This way it is not possible to see if there were any matches.
I would suggest an additional line, something like: Results were compared against x matches, just to make sure the query filters are working properly.