[TASK] Provide Metadata within existent modules

[ghost]

Background

The initial plan was to provide a fully redesigned mm-vault module (https://github.com/lazaridiscom/mm-vault). Due to the circumstances, this plan was dropped. This Issue adapts to the new situation.

https://github.com/lazaridiscom/mm-vault#b-integrate-mm-vault-to-main-project-metamask-extension

Description

In order to allow the account-related UI to be generated dynamically, some smaller changes need to be applied to the existent mm-wallets (current naming: keyring classes).

Those additions are non-breaking, thus applying them is non-critical. Here the draft implementation:

• https://github.com/lazaridiscom/mm-vault/blob/master/index.js#L20
• https://github.com/lazaridiscom/mm-vault/blob/master/index.js#L77
• Provide Generic AccountsNew UI Menu Entries #3666 (see commit 82ae138)

In essence, this is not more that adding some metadata to the account-providers (keyring classes). This metadata is then used by the UI subsystem to generate the UI during runtime (not knowing what classes are currently available).

Suggestions

This implementation should be done by @bitpshr (who can alternatively decide to continue the mm-vault redesign, which btw. would be a nice starting-point for TypeScript introduction).

Pitfalls

This task will most possibly emit a cascade of requirements to the main source-code / project.

[bdresser]

Closing due to inactivity. please let us know if you'd like to continue the discussion!