Update router bridge and add option for reuse_query_fragments

[BrynCooke]

A new option has been added to the Router to allow disabling of the reuse of query fragments. This is useful for debugging purposes.

supergraph:
  experimental_reuse_query_fragments: false

The default value depends on the version of federation.

Fixes #3452

Checklist

Complete the checklist (and note appropriate exceptions) before a final PR is raised.

• Changes are compatible[^1]
• Documentation[^2] completed
• Performance impact assessed and acceptable
• Tests added and passing[^3]
  • Unit Tests
  • Integration Tests
  • Manual Tests

Exceptions

Note any exceptions here

Notes

[^1]. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this.
[^2]. Configuration is an important part of many changes. Where applicable please try to document configuration examples.
[^3]. Tick whichever testing boxes are applicable. If you are adding Manual Tests:
- please document the manual testing (extensively) in the Exceptions.
- please raise a separate issue to automate the test and label it (or ask for it to be labeled) as manual test

[router-perf]

CI performance tests

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

[glasser]

For posterity — the description of this PR wasn't 100% right. The query fragment reuse feature (and the flag to disable it at the JS level) was introduced in Federation v2.1.0, not v2.4.9. What v2.4.9 introduced was a bug in that feature; its change was rolled back in v2.4.10.

The new router-bridge release contains both the 2.4.9->2.4.10 upgrade which rolls back the bug, and exposes the flag that disables the overall feature in Rust (with the default value being true as determined by the JS code).

My intention when exposing the flag was to keep the same default value (ie, router can pass reuse_query_fragments: None to router-bridge which means it would inherit the default value of true from JS), but that wasn't super clear in our communication.

So this PR here actually does more than remove the newly-added buggy aspect of the RQF feature — it actually completely disables it, which wasn't the intention. (The intention was to remove the new bug and let users turn the feature off, but not to change the feature's default enablement.)

I believe @BrynCooke is working on a PR to keep the default behavior the same now.