fix: catch coingecko errors

[DanielSchiavini]

• coingecko often fails due to 429 (rate limit) errors
• due to missing CORS headers we get no error details
• therefore, it's proper to catch all errors from coingecko
• related to fix: ignore 404's from prices API curve-frontend#1642

[0xAlunara]

Fetch promises only reject with a TypeError when a network error occurs. Since 4xx and 5xx responses aren't network errors, there's nothing to catch. You'll need to throw an error yourself to use Promise#catch.

A fetch() promise only rejects when the request fails, for example, because of a badly-formed request URL or a network error. A fetch() promise does not reject if the server responds with HTTP status codes that indicate errors (404, 504, etc.). Instead, a then() handler must check the Response.ok and/or Response.status properties.

I as explained in the comment, we do get a network error because of the missing CORS headers in the 429 response. CORS error causes fetch to generate an exception.