Define metadata to visually represent bridged assets

[hdevalence]

Problem

Currently, the Prax registry is used for assets that generally originate on an IBC chain, 1 hop away. However, very soon, we expect that it will also be used for assets with longer bridge paths. For instance:

• Eth via Axelar
• Bitcoin (via Nomic or Osmosis)

This is already potentially problematic, as Osmosis's token metadata defines an asset called "Bitcoin" which is not really Bitcoin, but a rehypothecated asset backed by many different bridges.

Policy

The Prax registry should show an asset with a badge representing a "via", if and only if the asset is determined not to be native to the source chain. This policy is intended to minimize confusion when showing "canonical" representations of assets, without imposing any opinionated choice of what representation is preferable when there are multiple possibilities

For example:

• USDC via Noble: no badge, USDC is natively issued on Noble
• ETH via Axelar: badge, ETH is being bridged via Axelar, and this is a choice of bridge
• USDC via Axelar: badge
• "BTC" via Osmosis: badge, this is a pooled asset

Proposed implementation

This is probably best to implement as a configuration data that specifies a list of overrides, since most IBC assets will not need to be badged, but some (like BTC on Osmosis) are labeled as being native when they aren't really.