Refactoring and improvements to support multiple bridges

[sept-en]

As we start to have multiple bridges in the repo already, it makes sense to have some sanity on it so both users and tools won't have controversial and misleading data for tokens.

Summary:

• Tokens list gen tool: add allbridge tag and rules;
• Define new rules for creating PRs;
• Update Allbridge-related files according to new rules.
• Update tokens list.

[paouvrard]

I was wondering if we need to include the network in tags, maybe using a single tag consisting of the bridge name is enough to differentiate tokens. For example UST is not native to Ethereum even if it was bridged from there via RainbowBridge so we could make a rainbowbridge tag.

[mfornet]

I was wondering if we need to include the network in tags, maybe using a single tag consisting of the bridge name is enough to differentiate tokens. For example UST is not native to Ethereum even if it was bridged from there via RainbowBridge so we could make a rainbowbridge tag.

Agree with this proposal, and created an issue for it (#87). @sept-en @karim-en lmk your opinion in this regard.

[sept-en]

@paouvrard @mfornet thanks for your suggestions! Let's continue the discussion in that mentioned issue.