test: cap helper get_service_info timeout in suppression test (~3.0s → ~1.85s)

[bdraco]

Summary

Part of #1707. Tests-only change.

The helper thread in test_get_info_suppressed_by_question_history calls zc.get_service_info with the default 3000ms timeout. Every query in this test is suppressed by the seeded question history, so no answer ever arrives — the helper sits at the full timeout. The three phase waits in the main thread sum to ~2.06s, so capping the helper at 1500ms is safe and lets the test finish in the phase-wait budget instead of the helper-timeout budget.

No production change.

Wall time:

• Before: 3.01s
• After: 1.85s

Test plan

• Targeted test passes under Cython build (REQUIRE_CYTHON=1)
• Full tests/ suite passes (337 passed, 3 IPv6 skips)
• Pre-commit hooks pass

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.76%. Comparing base (0deb56b) to head (2953144).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1708   +/-   ##
=======================================
  Coverage   99.76%   99.76%           
=======================================
  Files          33       33           
  Lines        3426     3426           
  Branches      471      471           
=======================================
  Hits         3418     3418           
  Misses          5        5           
  Partials        3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[codspeed-hq]

Merging this PR will not alter performance

✅ 6 untouched benchmarks

---

_{Comparing perf/tests-quick-question-suppression (2953144) with master (0deb56b)¹}

Footnotes

1. No successful run was found on master (6db1f91) during the generation of this report, so 0deb56b was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩