Improve Restoration and Update process

[louisinger]

Onboarding restoration

onboarding restoration is now responsible to fetch ALL the wallet data including:

• transactions + unblind them using masterBlindingKey
• assets details from registry
• block headers associated with transactions

the onboarding page is loading until that steps are all done.

it closes #457

Presenter layer

This PR also moves the StorageContext logic (all the useEffects used to create the frontend cache data) to application/Presenter (it lets to do not take care about framework stuff like rendering while writing the presentation update).

Mermaid triggers update

The Marina logo at the top-left of the popup becomes clikable on home page -> it triggers a repository update = scan the repos and try to fill holes (assets, transactions, blockheaders etc...)

@tiero please review

[tiero]

In the receive list we have duplicates

[tiero]

Can you split the commits into two PRs? One for the restoration only and one for the change application/Presenter, otherwise is hard to review and properly test changes to a specific layers.