Improve multi-chain support locally and move env variables to config

[tiagofilipenunes]

Please read the description to facilitate QA.

Proposed changes:

• Update to the way rpc url, headers, keys and .env variables are set:

  • Rpc url and headers have been moved to the config, with different development and production configs
  • There are now two types of rpc url and headers that can be defined. VITE_CHAIN_RPC_URL and config.rpc.url. If VITE_CHAIN_RPC_URL is not set, then config.rpc.url will be the one used for any network requests. For all cases, walletConnectRpc is used on wallet connection.
  • Remove VITE_CHAIN_RPC_URL - these env variables are already exposed in the network tab so no point in adding them. It also facilitates forks to set up their own development and production rpc urls. It was also not possible to set custom headers or key for the VITE_CHAIN_RPC_URL in case it was needed
  • Remove VITE_CHAIN_RPC_KEY as it was not used anymore
  • Note: Any fork will use the same rpc urls and headers set in the config. This is okay as the production ones are not expected to work (but can if they don't have a whitelist), and the development ones should be widely available or free rpc urls to facilitate running the app locally.

• The following .env variables were NOT moved to the config. Here are some discussion points about why not:

  • SDK
  • Variables: VITE_SDK_VERBOSITY and VITE_LEGACY_TRADE_BY_SOURCE_RANGE
    • Discussion
    • Makes it easy to set via deployments, obfuscating these options is good as they are optional and when required, the user will be familiar with them
    • SDK also expects env variables so we can keep a consistent behaviour with these flags in case some forks also run the SDK independently or check the documentation and are confused
    • Conclusion: No real benefit to adding them to config
  • Sentry
    • Variables: SENTRY_ORG, SENTRY_PROJECT, and SENTRY_AUTH_TOKEN
    • Discussion
      • Might be useful to add it here to make it obvious for projects wanting to use Sentry
      • Can add it to the readme instead
      • If someone forks the code, they will also port these variables and even though Sentry filters the origin domain, it's bad practice to let forks use these params as they are deployment-specific
      • It's much easier to change these settings via env variables without having to do a PR
      • Rotating keys would mean creating a PR which means better visibility for contributors
      • Conclusion: More points in favour of not adding to config
  • E2E
  • Variables: CI and TENDERLY_ACCESS_KEY
  • Conclusion: Do not move these to config as they are set by E2E CI and being able to override CI locally to produce screenshots is useful

• Facilitate local development in multiple chains but keep build process

  • start:network command as been added to the package.json with instruction in the readme on how to add it for forks
  • Local storage is partitioned by using the network when setting the keys as [APP_ID, NETWORK, APP_VERSION, key].join('-')
  • Clean-up of old locale storage keys added
  • VITE_NETWORK can still be used when starting and must be set when building

• Update github CI workflows:

  • Update build_test.yaml to remove unused env variables and update all actions to ones that default to using Node v20
  • Update e2e.yaml to remove VITE_CHAIN_RPC_URL as it is no longer used
  • Update test.yaml actions to ones that default to using Node v20

[cloudflare-pages[bot]]

Deploying carbon-app-sei with    Cloudflare Pages

Latest commit:	893c607
Status:	✅  Deploy successful!
Preview URL:	https://bd53c8e0.carbon-app-sei.pages.dev
Branch Preview URL:	https://add-quicknode-rpc.carbon-app-sei.pages.dev

View logs

[cloudflare-pages[bot]]

Deploying carbon-app with    Cloudflare Pages

Latest commit:	893c607
Status:	✅  Deploy successful!
Preview URL:	https://42afffad.carbon-app-csq.pages.dev
Branch Preview URL:	https://add-quicknode-rpc.carbon-app-csq.pages.dev

View logs