Increased user failsafe and security

As we all know, the blockchain and Bitshares platform is a platform where no authority have mandate to do transaction rolebacks if a user does something unintended. A user can be tricked to do a type of action that will result in loss of funds for the user.

So far, we've done things in various places of the application to improve the experience and security for the user, and mitigate any type of mistake done.

**This Epic Issue should track all related issues to user failsafe, trickery and security enhancements**

## Possible angles of trickery and mistakes

### Proposed actions
This became a problem last year, where users recieved proposed actions in their wallets. Some where to send funds, others where to change account authority. We've mitigated this by enabling the possibility to hide proposed actions by scam accounts, for example.

### Sending funds to an account with similar name, aka scam accounts
It's an old trick to create account names with very similar names, resulting in funds being sent to the wrong place. The list of scam accounts grows, and UX is improved to alert the user about it.

### Sending funds to an inactive account
[Reading about a user](https://bitsharestalk.org/index.php?topic=27730.0) that sent funds to an inactive account on the forum, makes me wounder if it's possible to add a warning when an account that hasn't been used for x months when doing transactions.

## Related Issues
- Label assets owned by 'known scammers' as scam assets - #2391

Start with the proposed-actions, similar-account, and inactive-account sections, then review related issue #2391. This is an epic rather than a scoped task, so a concrete enhancement and acceptance criteria must be identified before locating the relevant BitShares UI code; what counts as done is not defined here.

Written by the indexing model from the issue text.