Add SwiftNodes RPC endpoints to 57 EVM chains

[swiftnodes]

Adds SwiftNodes (https://swiftnodes.io) as an RPC option across 57 EVM chains. SwiftNodes provides flat-rate, no-KYC, crypto-payable RPC across 75+ chains. URLs use the standard ${SWIFTNODES_API_KEY} placeholder convention used by other keyed providers in this repo. Free tier and signup at swiftnodes.io.

[github-actions]

You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

[swiftnodes]

Pushed a follow-up commit addressing the two failing checks:

Prettier (12 files) — re-applied prettier --write to the chain files I had touched. The original commit was made with a custom text-insertion script that preserved formatting but didnt exactly match Prettiers expectations. Verified prettier --check _data/*/*.json now passes locally.

Build — the failure was unrelated to my SwiftNodes additions. The processor was crashing while validating chain 1s explorer URLs:

checking single chain _data/chains/eip155-1.json
Exception: java.net.ProtocolException: Too many follow-up requests: 21

I traced this to https://ethereum.dex.guru (one of chain 1s explorers) which currently returns a 25+ redirect loop:

$ curl -sIL --max-redirs 25 -A okhttp/4.12.0 https://ethereum.dex.guru
# 25 redirects, never settles

okhttp (used in Main.kts explorer check) trips its default redirect limit of 20 and throws, which isnt caught by a surrounding try/catch (unlike the RPC URL check that is). Any PR that touches chain 1 currently re-triggers this validation and gets blocked.

I removed only that one broken explorer entry. The other three explorers (etherscan, blockscout, routescan) cover the same use cases. Happy to split this into a separate PR if youd prefer to keep this one focused on the SwiftNodes additions — just let me know.

[swiftnodes]

Hit the same issue on chain 10 — dex.guru is broken across all chains it has explorers for (every subdomain either 404s or hits the redirect loop). Pushed one more commit that sweeps the same fix across the other 6 PR-touched chains that had dex.guru entries: 10, 56, 100, 42161, 7700, 8453.

If youd rather see dex.guru handled in a single dedicated PR (with all dex.guru-having chains at once, not just the ones I happened to touch in this one), happy to revert these explorer changes and open a separate cleanup PR.

[swiftnodes]

Pushed a cleanup commit that drops the unrelated changes and restores other files to master state. The PR now just adds a single SwiftNodes RPC URL per supported chain. Ready for re-review when convenient.

[swiftnodes]

Rebased onto current master — the earlier merge conflicts are now resolved into a single clean commit (RPC additions only, no collateral changes to other fields or files). Ready for review whenever you're able to approve the CI run. Thanks!