docs: Add extended reference reporting config

[Meschreiber]

Adds docs for extended reference reporting.

[github-actions]

@Meschreiber, please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

[router-perf]

CI performance tests

• reload - Reload test over a long period of time at a constant rate of users
• step-local-metrics - Field stats that are generated from the router rather than FTV1
• no-tracing - Basic stress test, no tracing
• events_callback - Stress test for events with a lot of users and deduplication ENABLED in callback mode
• xlarge-request - Stress test with 10 MB request payload
• events_big_cap_high_rate_callback - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity using callback mode
• events_without_dedup - Stress test for events with a lot of users and deduplication DISABLED
• events_without_dedup_callback - Stress test for events with a lot of users and deduplication DISABLED using callback mode
• step - Basic stress test that steps up the number of users over time
• step-jemalloc-tuning - Clone of the basic stress test for jemalloc tuning
• events_big_cap_high_rate - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity
• step-with-prometheus - A copy of the step test with the Prometheus metrics exporter enabled
• demand-control-instrumented - A copy of the step test, but with demand control monitoring and metrics enabled
• events - Stress test for events with a lot of users and deduplication ENABLED
• xxlarge-request - Stress test with 100 MB request payload
• large-request - Stress test with a 1 MB request payload
• demand-control-uninstrumented - A copy of the step test, but with demand control monitoring enabled
• const - Basic stress test that runs with a constant number of users

[abernix]

@bonnici @Meschreiber As this wasn't merged onto dev already, should this target our just created 1.50.0 release branch? If so, please rebase on that branch, or we need to be sure to cherry-pick in after this goes to dev. OR just merge it to main after next Tuesday if it just needs more time.

[Meschreiber]

Thanks @abernix ! Planning on completing it for review from @bonnici today and will retarget 1.50.0.

[Meschreiber]

@abernix , I'm note seeing said 1.50.0 branch yet, so @bonnici , would you just review on here and then I'll retarget or create a new docs PR once 1.50.0 is available.

(Unless I'm missing something!)

[abernix]

apologies. miscommunication upstream! We will make the 1.50.0 branch tomorrow ("today" in many places already 😉 )

[bonnici]

This explanation of the new checks functionality is great! Just one thing we could potentially add.

[Meschreiber]

Closing in favor of #5558