Cache resolved web3 provider endpoints

[YoshihitoAso]

📌 Description

This pull request introduces an endpoint URI cache for both FailOverHTTPProvider and AsyncFailOverHTTPProvider to optimize fail-over behavior and reduce unnecessary database lookups. It also adds a keep-alive HTTP session manager for async providers to improve connection reuse and efficiency.

✅ Related Issues

None

🔄 Changes

Fail-over provider improvements:

• Added a short-term cache for resolved endpoint URIs in both FailOverHTTPProvider and AsyncFailOverHTTPProvider, avoiding redundant database queries and improving performance during fail-over. The cache is automatically invalidated on connection errors or expiration.
• Refactored endpoint resolution and cache management logic into dedicated methods for clarity and maintainability.

Async provider connection management:

• Introduced KeepAliveHTTPSessionManager to ensure async HTTP sessions use keep-alive connections, reducing overhead for RPC-heavy workloads.
• Updated async fail-over provider to use the new session manager for connection pooling and cache management.

📌 Checklist

• I have added tests where necessary.
• I have updated the documentation where necessary.

[github-actions]

Coverage Report •

File	Stmts	Miss	Branch	BrPart	Cover	Missing
app/utils
web3_utils.py	312	82	66	30	73%	119, 126–129, 134–135, 138, 143–145, 149–152, 171–173, 177–178, 182–183, 187–188, 193–196, 199–200, 202, 210, 225–226, 237, 322, 330–331, 346–351, 353, 360–365, 367, 386–390, 395, 399–400, 403–407, 409–410, 414, 437–438, 456–458, 504, 508–509, 512–516, 523
tests/app/utils
web3_provider_cache_test.py	100	0	4	0	100%
TOTAL	37457	1470	3524	647	96%

Tests	Skipped	Failures	Errors	Time
1281	0 💤	0 ❌	0 🔥	10m 45s ⏱️