Add retry logic with exponential backoff and jitter for rate limits a…

[alex-omophub]

…nd server errors

• Introduced a new _calculate_retry_delay function to handle retry delays based on the Retry-After header and exponential backoff with jitter.
• Updated SyncHTTPClient and AsyncHTTPClientImpl to utilize the new retry delay calculation for handling rate limits (429) and server errors (502, 503, 504).
• Enhanced retry mechanism to improve resilience against temporary issues.

---

Summary by cubic

Add smarter retry handling for rate limits and transient server errors using exponential backoff with jitter. This improves resilience and respects server Retry-After guidance across both sync and async HTTP clients.

• New Features
  • Added _calculate_retry_delay() that honors Retry-After (up to 60s) or falls back to exponential backoff starting at 0.5s, capped at 8s, with 25% jitter.
  • Updated SyncHTTPClient and AsyncHTTPClientImpl to retry on 429, 502, 503, and 504 using the new delay logic.
  • Centralized retry constants and removed hardcoded sleep values.

^{Written for commit 9bf08d1. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

[codecov]

Codecov Report

❌ Patch coverage is 77.77778% with 6 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/omophub/_http.py	77.77%	4 Missing and 2 partials ⚠️

📢 Thoughts on this report? Let us know!