ui: rework app initialization

[buck54321]

This reworks app initialization to achieve a number of ux goals.

1. Adds chance for user to quickly configure native wallets and add
   known servers (view-only), client: allow skipping registration when adding a dex (view-only) #1986 (comment)
2. Adds seed backup dialog
3. Makes the Wallets view the landing page

[ukane-philemon]

Good work @buck54321. I will try testing this on my end.

[chappjc]

Very nice. Wallets above servers would be better for the multi-coin wallet pivot, but this is great either way.

[JoeGruffins]

Getting the same error as cli when trying to use:

$ ./dexc
failed creating web server: error loading localized html templates: error adding template init: template: init:35: comment ends before closing delimiter

[JoeGruffins]

Looks good. A few nits:

Cannot click the actual check boxes here. Can press anywhere else but not on the check boxes themselves.

"skip this for now" looks like it should be clickable but clicking it does nothing. It seems you cannot skip looking at the seed at all.

After just making the client and navigating to markets you will see this. I think there is an extra loading screen when you go the login route that waits for markets to load and so we don't ever get here in the ui normally. This page mus be reloaded at some point to show the markets.

Probably in master, but cannot view token markets without making a token wallet. I can see the eth market already with no eth wallet yet so not sure why it is different. On loading candles indefinitely.

[martonp]

Looks good other than the issues which @JoeGruffins also noticed.

[chappjc]

This is working very well for me with the last commit. Just some thoughts--

When you choose only to add wallets, no DEX host, we could add a link like this on the wallets page:

But that's not a new issue and not necessary. It could just be a plain <a href="/register">

The other thing, which is think is just a design decision, is when you add a DEX using this new interface, it's always "view-only" even if you had already had an account. We assume no account discovery by default is desirable. Should we? I restored from seed where I already had an account, and I saw:

And clicking discovered it so I got this simple form:

A slightly different approach that would avoid the need to add a "view-only" checkbox on this simplified init flow would be to first try assuming you want to discover an account, and then fall back to view-only if there was no known account. I don't think backend changes are needed for this.

Anyway, no need to make any changes. It works as-is! Thoughts? We can merge if there's no need to update in your mind.

[chappjc]

Pls squash/rebase and we can merge.

[chappjc]

Rebased and squashed for you so we can merge this since it has been good with approvals for a while.
I'd still like to know what you think about the ideas here but any more changes can wait.