fix: Handle pagination in chains API to fetch all chains

[gjeanmart]

📝 Summary

Fixes pagination handling in the chains API to fetch all available chains from the Safe Config Service.

🐛 Problem

The Safe Config Service API (https://safe-config.safe.global/api/v1/chains/) returns paginated results with a default limit of 40 chains per page. The current implementation only fetched the first page, which meant:

• Only 40 out of 41 available chains were displayed
• Any future additions beyond the initial page would not be loaded

✅ Solution

Updated the getChains function to handle pagination properly by:

• Implementing a while loop that iterates through all pages
• Following the next URL from each response until it becomes null
• Concatenating all results into a single array before returning

🔍 Changes

File: src/api/getChains.tsx

• Added pagination loop to fetch all pages
• Concatenate results from each page into allChains array
• Continue fetching until next is null

🧪 Testing

• Verified all 41 chains are now loaded
• ESLint passes
• No breaking changes to existing functionality

📊 Impact

• Before: 40/41 chains displayed (missing 1 chain)
• After: All 41 chains displayed correctly
• Future-proof: Will automatically fetch any number of chains as the list grows