docs: clarify enhanced signature generation might cause different operation ids

[Meschreiber]

Clarify enhanced signature generation may cause different operation ids

[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
• 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