remove iterations from test_reload_config_with_broken_plugin_recovery

[Geal]

that test is not flaky, but still takes 15s to do the same operation 3 times in a row

---

Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

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

[github-actions[bot]]

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

[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

[Geal]

my feeling is that it was flaky at the time so doing it 3 times increases the probability of triggering bugs. But the CI showed that this is not one of the flaky tests

[BrynCooke]

This test was meant to try and catch issues with telemetry reloading, particularly hangs, maybe we're confident enough now that we don't need the multiple iterations.