Mock Auth backend component for local dev

This would be similar in purpose to #882 .

By mocking the Auth component we would decrease new dev onboarding friction while also reducing the need to widely share the dev auth account secret.

If the AUTH_SECRET_KEY is not present it will use the mock, otherwise Auth0 itself.

Users specifically developing auth features would add the key and thus be able to work with the real thing. Those not needing to, can just rely on the mock so they can get on with developing other features.

A few notes on likely implementation:

• All we would be mocking are the methods used in /auth/login https://github.com/FightPandemics/FightPandemics/blob/ad05066e1ae4375c0d7045779c4c329faa44c5c8/backend/lib/endpoints/auth.js#L117
• It’ll only easily work with email/password, not social since we’d need to mock the oauth providers (more complicated than it’s worth for purpose of this issue
• Idea is dev just goes to login (no sign-up). The password is handled by Auth0 and not stored in our DB so we’ll just ignore it with the mock. ~If the user exists they will be logged in. If they don’t exist they will be signed-in and then proceed to create their profile as usual which saves the user to the database.~ A better idea is that we add 5 users via DB seeding for local dev - we can use https://github.com/pkosiec/mongo-seeding and run this as part of Dockerfile.dev build step.

[galeza]

Hi @vnessa-su @joshmorel I think that this solution will also be ideal for automation tests.

@jessica-lau Issue important for automation QA team 😃

[galeza]

@joshmorel Thank you!