feat: adds shared rate limiting to the relay using Redis

[simzzz]

Description:
This PR refactors the rate limiting logic in our JSON-RPC relay service to support both local (LRUCache) and distributed (Redis) backends. The changes include:

• Introducing a new RateLimiterService class with a pluggable backend system.
• Defaulting to Redis for centralized rate limiting across multiple pods, with a fallback to LRUCache if Redis is unavailable.
• Enhancing configuration handling to support future backend extensions like Hazelcast or Memcached.
• Implementing a "fail fast" approach by throwing a ConfigurationError if a required client is missing.
• These improvements aim to make the rate limiting system more flexible and scalable.

Related issue(s):

Closes #3780, closes #3781, closes #3782

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[lfdt-bot]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[github-actions]

Test Results

 22 files  ±  0  289 suites   - 6   21m 26s ⏱️ - 16m 31s
664 tests + 15  657 ✅ + 14  5 💤 ±0  2 ❌ +1 
868 runs  +123  859 ✅ +122  7 💤 +2  2 ❌  - 1 

For more details on these failures, see this check.

Results for commit ff30194. ± Comparison against base commit d45744b.

This pull request removes 5 and adds 20 tests. Note that renamed tests count towards both.

Should reset limit for requests ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Rate Limit Tests Should reset limit for requests
Should submit batch requests to WS server and receive IPRateLimitExceeded error until rate limit is reached ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Rate Limit Tests Should submit batch requests to WS server and receive IPRateLimitExceeded error until rate limit is reached
Should submit single requests to WS server and receive IPRateLimitExceeded error until rate limit is reached ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Rate Limit Tests Should submit single requests to WS server and receive IPRateLimitExceeded error until rate limit is reached
should not throw rate limit exceeded error for eth_chainId ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Rate Limiters Acceptance Tests RPC Rate Limiter Acceptance Tests Given requests within the Tier 2 rate limit should not throw rate limit exceeded error for eth_chainId
should throw rate limit exceeded error for eth_chainId ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Rate Limiters Acceptance Tests RPC Rate Limiter Acceptance Tests Given requests exceeding the Tier 2 rate limit should throw rate limit exceeded error for eth_chainId

should distribute WebSocket requests across services without interference ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Shared Rate Limiting Acceptance Tests Shared WebSocket Rate Limiting Between Services should distribute WebSocket requests across services without interference
should distribute requests across services without interference ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Shared Rate Limiting Acceptance Tests Shared Rate Limiting Between Services should distribute requests across services without interference
should handle concurrent WebSocket requests from both services ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Shared Rate Limiting Acceptance Tests WebSocket Service Independence and Failover should handle concurrent WebSocket requests from both services
should handle concurrent requests from both services ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Shared Rate Limiting Acceptance Tests Service Independence and Failover should handle concurrent requests from both services
should handle mixed single and batch requests across WebSocket services ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Shared Rate Limiting Acceptance Tests WebSocket-Specific Rate Limiting Scenarios should handle mixed single and batch requests across WebSocket services
should immediately rate limit on serviceB after serviceA hits the limit ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Shared Rate Limiting Acceptance Tests Shared Rate Limiting Between Services should immediately rate limit on serviceB after serviceA hits the limit
should immediately rate limit on wsServiceB after wsServiceA hits the limit ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Shared Rate Limiting Acceptance Tests Shared WebSocket Rate Limiting Between Services should immediately rate limit on wsServiceB after wsServiceA hits the limit
should maintain independent Redis connections for WebSocket services ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Shared Rate Limiting Acceptance Tests WebSocket Service Independence and Failover should maintain independent Redis connections for WebSocket services
should maintain independent Redis connections ‑ RPC Server Acceptance Tests Acceptance tests @ratelimiter Shared Rate Limiting Acceptance Tests Service Independence and Failover should maintain independent Redis connections
should maintain rate limiting consistency during WebSocket connection handoffs ‑ RPC Server Acceptance Tests Acceptance tests @web-socket-ratelimiter Shared Rate Limiting Acceptance Tests WebSocket-Specific Rate Limiting Scenarios should maintain rate limiting consistency during WebSocket connection handoffs
…

♻️ This comment has been updated with latest results.

[konstantinabl]

Some changes needed

[quiet-node]

Great work as always and appricate the efforts.

[quiet-node]

Nice I think it looks good just one item.

[quiet-node]

LGTM great work!