http: add 429 rate-limit handling with host-level cooldowns

[liquidsec]

Summary

• When the http module's batch stream receives a 429, it defers the event and sets a per-host cooldown using the Retry-After header (default 30s, capped at 60s)
• Deferred events re-enter the queue after their cooldown expires, bypassing dedup via is_incoming_duplicate override
• Gives up after 3 retries per URL to prevent infinite loops
• Overrides finished property so deferred events keep the scan alive during cooldowns
• Uses existing 429_sleep_interval / 429_max_sleep_interval config values from the API 429 handler
• Non-blocking: other hosts in the same batch proceed normally while one host is cooled down

Tested against a local rate-limiting server (429 after 5 requests, 3s Retry-After) and against stackoverflow.com under Cloudflare rate limiting.

[github-actions]

🚀 Performance Benchmark Report

⚠️ No current benchmark data available

This might be because:

• Benchmarks failed to run
• No benchmark tests found
• Dependencies missing

[codecov]

Codecov Report

❌ Patch coverage is 89.47368% with 14 lines in your changes missing coverage. Please review.
✅ Project coverage is 90%. Comparing base (b795c7c) to head (36013dd).
⚠️ Report is 79 commits behind head on dev.

Files with missing lines	Patch %	Lines
bbot/modules/http.py	87%	14 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             dev   #3145     +/-   ##
=======================================
- Coverage     90%     90%     -0%     
=======================================
  Files        449     453      +4     
  Lines      44435   46024   +1589     
=======================================
+ Hits       39762   41152   +1390     
- Misses      4673    4872    +199     

☔ View full report in Codecov by Harness.
📢 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.