chore(maint): Update code and snapshots after proto update

[bonnici]

Updates code and snapshots so that we store default values in the new proto fields.

[router-perf]

CI performance tests

• 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
• const - Basic stress test that runs with a constant number of users

[abernix]

I've opened up #5029 to land this on 1.45.1. I'll also note that we've introduced #5031 and #5030 to remove the "proto has changed? here, have a failing dev branch to go with that" behavior, which should hopefully make it way less necessary for you to time your contributions to this repository and mostly just require that you wait until the next "5 minute" interval and find the chore Update Apollo Protobuf PR like the one referenced above.

[abernix]

For whatever reason, this landed cleanly and passed CI on #5029 — which targeted 1.45.1, whereas tests are refusing to pass on this PR. I'm unable to tell why.

[abernix]

Superseded by #5032, which did work and land. Best guess is CI cache is just busted on this PR because of underlying issues that existed on dev on the day it was built.