Redesigned unlock success

[overheadhunter]

Replaced the green "welcome back, alice" screens with more useful messages and matching the design of the remaining page.

Also added a new state when unlocking a vault after migrating to 1.3.0, when the account requires setting up user keys.

Note

Not yet localized, as we require to guess the browser language, first.

when oauth failed

when user didn't complete setup yet

when the app needs registration

either on a known browser:

or when the browser is unknown:

403

success

[SailReal]

LGTM 👍

Just one thing I noticed and wanted to mention, but I'm totally fine with, is that with a successful legacy device unlock, the "when user didn't complete setup yet" variant is shown, but this is perfectly fine imo, because even if the user has set up their user keys, they can still use the legacy unlock.

[infeo]

I suggest to change the wording of the "Setup Required" screen, the "few simple steps" sounds very vague and not reassuring. I plead for keeping it simple:

To unlock, you need to setup your account.

And then also update the button description, because "Complete setup" sounds like the user already started:

Setup Account

[overheadhunter]

I suggest to change the wording of the "Setup Required" screen, the "few simple steps" sounds very vague and not reassuring. I plead for keeping it simple:

To unlock, you need to setup your account.

Actually, legacy unlock may work, as Julian mentioned above. Nevertheless users shall complete setting up the account keys.

But I'll get rid of the "few simple steps", it really is just a single step anyway.

And then also update the button description, because "Complete setup" sounds like the user already started:

Setup Account

This also affects users who already have an account, thus it would sound as if their account was deleted. Thus I'll keep the "Complete" metaphor to not slow this PR down, but am open for other suggestions.