STOR-5489: Implement retry loop for actor fetch requests

[apeacock1991]

When the enforcement gate is enabled, we now attempt to retry disconnected actor requests within the following bounds:

• The request is eligible for retries (e.g. is fetch, is rewindable, is WebSocket upgrade request)
• Retry up to maximum of 5 times
• Retry up to a maximum of 10 seconds, with backoff

There's some cleanup in this PR too:

• Renamed supportsActorRetryMetadata to supportsActorFetchRetries, ultimately this is what we care about vs metadata
• Extracted out some existing tests to a new test suite that is specifically for retries

Descoped from this PR:

• Replicas, which I'll tackle separately (there is some complexity around their channel)
• Adjusting how subrequests counts/metrics are handled (we won't count retries in the request-based limit)

[codspeed-hq]

Merging this PR will degrade performance by 9.24%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 1 regressed benchmark
✅ 71 untouched benchmarks
⏩ 129 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	simpleStringBody[Response]	22.4 µs	24.7 µs	-9.24%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing apeacock/stor-5489-replay (0cec5a1) with main (6dd2348)}

Footnotes

1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩