fix: update USDC address on Celo Alfajores testnet

[arthurgousset]

Currently, the USDC address specified for Celo Alfajores testnet is incorrect.

interface/apps/web/src/constants/tokens.ts

Lines 481 to 482 in 1ffb970

	[ChainId.CELO]: USDC_CELO.address,
	[ChainId.CELO_ALFAJORES]: USDC_CELO.address,

The correct USDC addresses are:

1. Celo (mainnet): 0xcebA93...
2. Celo Alfajores (testnet): 0x2F25de...

- [ChainId.CELO_ALFAJORES]: USDC_CELO.address,
+ [ChainId.CELO_ALFAJORES]: USDC_CELO_ALFAJ0RES_NATIVE.address,

  export const USDC_CELO_NATIVE = new Token(ChainId.CELO, '0xcebA9300f2b948710d2653dD7B07f33A8B32118C', 6, 'USDC', 'USDC')
+ export const USDC_CELO_ALFAJ0RES_NATIVE = new Token(
+  ChainId.CELO_ALFAJORES,
+  '0x2F25deB3848C207fc8E0c34035B3Ba7fC157602B',
+  6,
+  'USDC',
+  'USDC CELO Testnet'
+ )

[arthurgousset]

TLDR:

1. Uniswap Labs will host the Celo subgraph used in production, and
2. Uniswap Labs will own and maintain the v3-subgraph repo that generates the subgraph.

On that basis, community members can request new tokens to be whitelisted by opening a PR in the v3-subgraph repo.

@mzywang expects the new Celo subgraph will be live and used in production in the order of "weeks" (not days or months).

For future reference:

• The subgraph affects optimal order routing, Uniswap uses the subgraph for pool discoverability and ranks pools based on TVL.
• If the subgraph is down (as is the case right now for the one on the hosted service), a static list of tokens is used to determine routes defined in the uniswap interface.

Source: celo-org/uniswap-v3-info#1 (comment)

On that basis, I'll close this PRs, since all work streams here are and will be owned by Uniswap.