Fix: Use correct asset platform when calling CoinGecko

[davecreaser]

Description

• Use the network_id environment variable to determine which asset platform should be used while calling the CoinGecko api.

Testing

A little trickier to test properly, but there's some things you can do:

• Go to the balances table and refresh the page with the network tab open in dev tools.
• If you check the network tab you should find some calls to the CoinGecko api:

• ChangeNETWORK_ID="ganache" in your .env.local file to be NETWORK_ID="gnosis"
• Repeat the first two steps
• You should now see the call being made with xdai instead of arbitrum-one as the asset platform

The main idea here is that on production, it is currently incorrectly calling with xdai as the asset platform, whereas it should be using arbitrum-one. The network_id environment variable on production is arbitrumOne.

Diffs

Changes 🏗

• Update the CoinGecko config to use the network_id environment variable to determine which asset platform should be used when calling the api.

Resolves #2418

[rdig]

@bogdan-1337 why did you make this commit 290da64 on this branch ?

Is this for arbitrum or gnosis ?

[iamsamgibbs]

This looks good to me! Changes make sense and tested using the steps provided.

[rumzledz]

Nice one @davecreaser , I learnt something new while reviewing this PR 😎

• NETWORK_ID="ganache"
  

• NETWORK_ID="gnosis"
  

[rdig]

Changes look good. Initial knee jerk reaction would be to tell you to default to Gnosis, not Arbitrum since this will be merged into master and that is still a gnosis default branch.

However soon that won't be the case and I won't fight too much against this.

However I'm still curious about the change that @bogdan-1337 pushed to this branch, and especially if it needs a similar change on the master-arbitrum side

[bogdan-1337]

@bogdan-1337 why did you make this commit 290da64 on this branch ?

Is this for arbitrum or gnosis ?

Updated the version for the action, it was causing issues for the build on this branch, but not for other branches so not sure what that's about, but anyway good to have it updated to the new version so can be merged to any branch.