Wallet attribute: Security history

[polymutex]

This issue is about adding a new Security attribute which focuses on a wallet's history of security (or of hacks).

This is especially relevant for hardware wallets, but we should try to make the attribute apply to software wallets as well if possible.

For L2s or smart contract, "security history" can often be measured in terms of "area under the curve" of TVL. For wallets, there is no direct analog to this, but hopefully we can find something similarly empirical in nature.

Q: Should we track hacks of wallets specifically, or also include hacks of wallet development companies?
Argument: Hacks of wallet development companies may be a reflection on their security practices in general. They have implications for e.g. software supply chain security (what if their build machine gets compromised?). Additionally, depending on the nature of the hack, they may also have user implications (e.g. Ledger database hack which made public the street addresses of many large crypto holders).