Investigate unstable performance-test SLAs

[ReToCode]

Context

PR #14289 made performance tests work again. There has been some discussion on follow-up improvements.
PR #14429 added a new SLA to check if the expected rates match the actual rates.
Unfortunately, the performance test SLAs were never really stable in various builds, so we should look into that topic separately.

Goals

• Adapt the performance-tests so that results are stable between multiple runs
• Optionally update the SLA values
• Fail the performance-test build if an SLA is breached

Previous discussions see:

• Add Vegeta rates / targets to SLA in performance tests #14429 (comment)
• Add Vegeta rates / targets to SLA in performance tests #14429 (comment)
• Add Vegeta rates / targets to SLA in performance tests #14429 (comment)

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.