Add coingecko_id to asset metadata

[erwanor]

In penumbra-zone/penumbra#5000 we added a coingecko_id to the Metadata proto. Now, we should augment the penumbra-1 registry entries with an associated id:

  ATOM: "cosmos",
  btc: "bitcoin",
  eth: "ethereum",
  TIA: "celestia",
  OSMO: "osmosis",
  USDC: "usd-coin",
  WBTC: "wrapped-bitcoin",
  BTC: "bitcoin",

This will let us amend and merge penumbra-zone/penumbers#16 which was kindly done for us.

This means we have to:

1. Bump the protos
2. Augment the registry
3. Publish it

It would be very helpful to document each steps to facilitate collaborations with other teams

[vacekj]

Since the CoinGecko API that serves all of the supported tokens and their addresses is behind a paid plan, I am going one by one and adding the ids manually for each token. Some of the tokens, like COOK, are not listed on CoinGecko, leaving those fields blank.

managed to get a free API key, querying the coingecko api automatically now. also here's all of their supported coins in a gsheet: https://docs.google.com/spreadsheets/d/1wTTuxXt8n9q7C4NDXqQpI3wpKu1_5bGVmP9Xz0XGSyU/edit?gid=0#gid=0

[vacekj]

1. added all relevant ids from the sheet mentioned above.
2. updated the penumbra crates names and commit shas to the commit that introduces the coingecko_id field.
3. Made a PR to core to add the coingecko_id field to the Metadata struct that processor.rs works with (relevant discussion here) - asset: add coingecko_id to Metadata struct penumbra-zone/penumbra#5007
4. After that PR is merged, will finish and merge this one.