Resolves #356.
Based on #564.

Note: This is based on #564 - you can either review them separately or just review this one. Be aware that the change set is rather large. Unfortunately, this could not be avoided due to the deep impact of the new behaviour on nearly all components.

Before this commit, a request to API endpoint /display was always triggered on almost every page load.
After this commit, the request to /display is made when necessary.

Users have reported that on mainnet, this request alone can take up to ~20 seconds!
The speed increase is also very noticeable on regtest in your dev environment.

Behaviour before

Requests to /display were done when:

• After initial loading of wallet
• navigating to MainWalletView
• navigating to Send
• navigating to Earn
• navigating to Jam
• freezing/unfreezing of UTXOs

Behaviour now

Requests to /display are done when:

• After initial loading of wallet
• opening JarDetails Overlay
• attempting to create a Fidelity Bond

However, there are trade-offs! Now, one must know which data is needed on the current screen as opposed to just reloading all data. i.e. if addressSummary is needed, data from /display still has the be loaded.

Also, it can be that the user is not warned when an address is reused. This is the case after sending to an own address. Before, if a second attempt to send to the same address is made, a user has seen a warning. Now, this warning is not displayed anymore. It can be mitigated by also scanning the UTXO addresses (not done in this PR!).

How to test

You can compare new and past behaviour by clicking through the UI on localhost:3000 (new behaviour) and on localhost:29080 (past v0.1.2 behaviour). If you open these in two windows next to each other, the speed increase becomes apparent.