MBL-1169: Redirection step

[Arkariang]

📲 What

• On AuthorizationStep the authorization URL is generated adding PKCE parameters to the url
• On redirectionStep an appplink redirects back to the app, so far the redirection only contains code, not ready yet to call the token endpoint (WIP) on the backend side.

🤔 Why

• OAuth 2.0 on the apps

🛠 How

• The VM now receives an Intent is able to build the authorization URL is staging and production on the AuthorizationStep
• the VM now receives an Intent and is able to collect from it the code that will be used later on to call the Token endpoint.
• OAuthActivity registers the redirectionUrl deeplink.
• Added tests
• Added an Interface wrapper on CodeVerifier to be able to mock it on tests.

👀 See

• Chroma tab should be able to load AuthorizationUrl
• Once the user has introduced email + password the redirection back to app enters in place back to a currently empty OAuthActivity

LogIn.mp4

| | |

📋 QA

• Turn the ff on, try to log in, the ChromeTab will load a formulary, once successful user + password introduced the user is redirected back to the app, to an empty OAuthActivity for now.
• You can also take a look at logcat filtering by package:mine level:debug OAuth, and look for the debug messages showing the AuthorizationStep + url to load, and the TokenRetrieveStep + code

Story 📖

MBL-1168