Use tags to specify native network, previous network and used bridge

[mfornet]

There are some tokens that are native to some chains, but were bridged to NEAR/Aurora through some intermediate chains. This is currently the case for UST, it is native from Ethereum, but was bridged to NEAR from Terra. To be explicity in this regard we can have more informative tags with key/values (not all the tags needs to follow this pattern, but it is useful to disambiguate when values can have different meanings).

Example of some tags:

"tags": {
    "native:ethereum": {
      "name": "Native Ethereum",
      "description": "Tokens that are native to Ethereum network"
    },
    "predecessor:terra": {
      "name": "Predecessor Terra",
      "description": "Tokens bridged from Terra, but not necessarily native there."
    },
    "bridge:allbridge": {
      "name": "Bridge AllBridge",
      "description": "Tokens bridge using allbridge"
    },
}

[sept-en]

I like the idea! The only thing I wanted to change, that the UST example it's actually native to Terra but not native to Ethereum. But the token that is used has ERC-20 token in Ethereum.

Having these tags would be definitely useful, even if we don't display these in any front-ends, back-ends could use those to build appropriate usesful and more meaningful representation.