E2E: Verifying Users

[lampholder]

This can all be implemented independently of the bidirectional verification flow work. (I'm in favour of doing so so we don't have to tackle both a new front- and back-end flow at the same time).

• [ ] Make the member info look like the wireframe (1 - barring answering the question "what do we do with all the other memberinfo UX we have today")
• [ ] Put a QR code in the Cryptography section of the existing user settings (1)
• [ ] Monodirectional QR code verification flow (3)
• [X] Monodirectional SAS text verification flow (using the existing encoded 32 byte code)

[nadonomy]

Note: I'll solve:

barring answering the question "what do we do with all the other memberinfo UX we have today"

With some more long-term thinking designs that we're working on in parallel for the redesign.