chore: Update Apollo Protobuf

[github-actions[bot]]

trafficstars

This updates the copy of reports.proto which this repository relies on with the latest copy fetched via our public endpoint.

[router-perf[bot]]

CI performance tests

• [x] step - Basic stress test that steps up the number of users over time
• [ ] 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
• [ ] large-request - Stress test with a 1 MB request payload
• [ ] events - Stress test for events with a lot of users and deduplication ENABLED
• [ ] xxlarge-request - Stress test with 100 MB request payload
• [ ] events_without_dedup - Stress test for events with a lot of users and deduplication DISABLED
• [ ] xlarge-request - Stress test with 10 MB request payload
• [ ] step-jemalloc-tuning - Clone of the basic stress test for jemalloc tuning
• [ ] events_callback - Stress test for events with a lot of users and deduplication ENABLED in callback mode
• [ ] no-graphos - Basic stress test, no GraphOS.
• [ ] reload - Reload test over a long period of time at a constant rate of users
• [ ] 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
• [ ] events_without_dedup_callback - Stress test for events with a lot of users and deduplication DISABLED using callback mode
• [x] const - Basic stress test that runs with a constant number of users

[abernix]

As to context about this new mechanism, we've introduced https://github.com/apollographql/router/pull/5031 and https://github.com/apollographql/router/pull/5030 and this is the first output from that.

[abernix]

Tests will fail on this PR until we actually apply what @bonnici tried to apply in https://github.com/apollographql/router/pull/5026 but for whatever reason haven't been able to pass because of a failing integration::lifecycle::test_shutdown_with_idle_connection test.

[github-actions[bot]]

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