Catch Infura 429 errors

[rarecrumb]

Describe the bug
We hit a rate-limit for Infura RPC and receive a 429

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Specs:

• OS: Kubernetes 1.30
• Kernel: [e.g. Linux 6.2.0-27-generic]
• Blutgang version: latest
• Please add any specs relevant to your issue below

Blutgang options:

• DB mode: [e.g. HighThroughput]
• DB compression: [e.g. no]
• Cache capacity: [e.g. 1000000000]
• MA length: [e.g. 20]
• RPCs used: infura

Additional context

error={ "code": -32005, "data": { "see": "https://infura.io/dashboard" }, "message": "daily request count exceeded, request rate limited" }, payload={ "id": 12449, "jsonrpc": "2.0", "method": "eth_blockNumber", "params": [  ] }, code=UNKNOWN_ERROR, version=6.12.1)

[makemake-kbo]

I think this addressed it a5ae3b9

[makemake-kbo]

it was actually this... c334a61