docs(qa/v1): Report on saturation point and 200-nodes test (backport #2667)

[mergify]

Closes #2461, #2513

This report includes results for tests with and without latency emulation.

Rendered

---

PR checklist

• Tests written/updated
• Changelog entry added in .changelog (we use unclog to manage our changelog)
• Updated relevant documentation (docs/ or spec/) and code comments
• Title follows the Conventional Commits spec

---

This is an automatic backport of pull request #2667 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 53e6127 has failed:

On branch mergify/bp/v1.x/pr-2667
Your branch is up to date with 'origin/v1.x'.

You are currently cherry-picking commit 53e612794.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   docs/references/qa/CometBFT-QA-v1.md
	modified:   docs/references/qa/README.md
	new file:   docs/references/qa/img38/200nodes/avg_mempool_size_ylim.png
	new file:   docs/references/qa/img38/200nodes/block_size_bytes.png
	new file:   docs/references/qa/img38/200nodes/memory_ylim.png
	new file:   docs/references/qa/img38/200nodes/mempool_size_max.png
	new file:   docs/references/qa/img38/200nodes/rounds_ylim.png
	new file:   docs/references/qa/img38/200nodes/total_txs_rate_ylim.png
	new file:   docs/references/qa/imgs/v1/200nodes/latencies/e_8e4e1e81-c171-4879-b86f-bce96ee2e861.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/avg_cpu.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/avg_memory.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/avg_mempool_size.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/block_rate.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/block_rate_regular.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/block_size_bytes.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/blocks.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/cpu.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/memory.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/mempool_size.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/mempool_size_max.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/peers.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/rounds.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/total_txs.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/total_txs_rate.png
	new file:   docs/references/qa/imgs/v1/200nodes/metrics/total_txs_rate_regular.png
	new file:   docs/references/qa/imgs/v1/200nodes/v1_report_tabbed.txt
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/latencies/e_8190e83a-9135-444b-92fb-4efaeaaf2b52.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/avg_cpu.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/avg_memory.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/avg_mempool_size.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/block_rate.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/block_rate_regular.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/block_size_bytes.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/blocks.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/cpu.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/memory.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/mempool_size.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/mempool_size_max.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/peers.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/rounds.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/total_txs.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/total_txs_rate.png
	new file:   docs/references/qa/imgs/v1/200nodes_with_latency_emulation/metrics/total_txs_rate_regular.png
	new file:   docs/references/qa/imgs/v1/saturation/saturation-plotter-LE.py
	new file:   docs/references/qa/imgs/v1/saturation/saturation-plotter.py
	new file:   docs/references/qa/imgs/v1/saturation/saturation_v1_LE.png
	new file:   docs/references/qa/imgs/v1/saturation/saturation_v1_v038.png
	new file:   docs/references/qa/imgs/v1/saturation/throughput_vs_latencies_v1_with_LE.png
	new file:   docs/references/qa/imgs/v1/saturation/throughput_vs_latencies_v1_without_LE.png

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   scripts/qa/reporting/prometheus_plotter.py

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally