💪 Increase checks for scanned QR code

[Abby-Wheelis]

In order to ensure that only valid users are created, we need to make sure that the qr codes that are scanned: are QR codes, have not been canceled, start with the appropriate prefix (either emission or nrelopenpath), and include a token parameter.

This way, after we scan into the app, we are sure that the user has scanned the right thing and will have a valid opcode. Later in the login process, we check the opcode for validity.

I still need to test this with a physical phone before it can be merged, which I plan to do tonight.

[Abby-Wheelis]

While testing this, I discovered that the QR code on the "save qr" page is not composed with a full URL, only the opcode. I'll work up a fix now.

[Abby-Wheelis]

Fix up for the QR code being created with opcode and not whole link in onboarding. In the QrCode component, I added a check to see if the value was a url, and if not, prefix the value with "nrelopenpath://login_token?token=".

Checks have been added when the code is scanned. I chose to check for "nrelopenpath" or "emission" to accomodate the dev environment, but open to changing this. The reason I did not condition what I check for on the global __DEV__ flag is that sometimes we login to the devapp with production opcodes for testing, but if we want I can add that condition, and we can just know to modify the code if we want to use the devapp to scan an qr code that starts with "nrelopenpath"

[shankari]

Let's keep this as emission in the public repo, I will change it to nrelopenpath in the internal one.
Long term, this should be part of the app config
e-mission/e-mission-docs#985 (comment)