[GoodBounty] Finalize fetchAndTestRpcs fix PR

[L03TJ3]

[GoodBounty] Finalize fetchAndTestRpcs fix PR

Summary

Pick up the existing AI-generated PR #638 for fetchAndTestRpcs RPC parsing hardening, run it locally, fix implementation gaps, update tests/evidence, and prepare it for human review.

Contributor role reference:
https://docs.gooddollar.org/for-developers/contributing/open-source-contributors/contributor-role

Contributor task

• Claim the bounty with an ETA.
• Check out the PR branch (copilot/fix-fetch-and-test-rpcs-failure) and run it locally.
• Compare the implementation against parent issue #637 and verify the parsing fix is robust.
• Fix concrete gaps in behavior, tests, and code quality.
• Leave a handoff comment with what changed, what was tested, and remaining risks.

Scope checks

Breakdown specific to the fetchAndTestRpcs parsing bug and PR #638

• the solution should be heavily simplified and easy, not over-engineered, straight-forward
• The PR solves the issue requirements from [Plan] Bug: fetchAndTestRpcs failing #637 (brittle parsing fails → safe parsing + deterministic fallback).
• fetchAndTestRpcs no longer uses eval() or fragile regex on the DefiLlama JS source file.
• FALLBACK_RPCS_BY_CHAIN is used as fallback when fetch, parse, or test fails for any chain.
• rpcInitializationPromise is reset to null on failure so the app can retry without a full page reload.
• rpcParsing.ts correctly extracts HTTP(S) RPC URLs for all required chains: 1, 122, 42220, 50.
• rpcParsing.test.ts live-fetch test passes against the current DefiLlama chainlist source.
• Existing repo patterns in src/hooks/useWeb3.tsx are respected (no unrelated changes).
• Happy path (cache miss → fetch → parse → test → cache) and error path (fetch/parse fails → return fallback) both work end-to-end.
• The PR description links [Plan] Bug: fetchAndTestRpcs failing #637 and includes test evidence (test output logs or screenshot).

Required commands

pnpm install
pnpm build
pnpm lint
pnpm test

If a command cannot be run, document why.

[dzkjdxhbgog]

/attempt #639

ETA: I’m starting now. Plan: check out PR #638’s branch locally, compare it against #637, harden the parser/fallback behavior where needed, run the available pnpm commands, and either update with a clean follow-up PR or document the exact blocker if upstream branch permissions prevent direct updates.

[franklinnweke]

Claiming this. ETA: I’ll inspect PR #638 against #637, run the relevant checks locally, patch concrete gaps, and report back with test output within the next few hours.

[L03TJ3]

@dzkjdxhbgog Before doing any work you are expected to read up on our rules and contributors program:
https://docs.gooddollar.org/for-developers/contributing/open-source-contributors

As long as you don't have priority access as contributor you are expected to wait to be assigned any issue.

Pull-requests from new contributors that don't have priority access are not going to be reviewed and are not up for bounties

[L03TJ3]

Same for you @franklinnweke

[Gutopro]

Hi @L03TJ3 can I work on this?

[L03TJ3]

@Gutopro Yes, you are assigned now.
make sure to also accept invite to collaborate on the repository else you cannot open pull-requests.
And make sure to be up to date with the new bounty flow

[L03TJ3]

I did add a note which was missing: This bounty is about simplifying, simple solution to the problem.
AI overdid it likely, but has to be verified and tested.
also make sure you are using the new hand-off template: https://github.com/GoodDollar/GoodWidget/blob/main/docs/contributor-bounty-template.md#handoff-comment
@Gutopro