User can be signed in with database not yet updated

[nickmeinhold]

Describe the bug The user can be signed in but the database hasn't yet been updated due to long cloud function cold starts.

To Reproduce Steps to reproduce the behavior:

0. Ensure no account already exists for your auth provider
1. Sign in (so a new account is created)
2. Observe Avatar image / Go to Profile (observe waiting indicators)
3. Create a conversation
4. See error

Expected behavior

Possible Solutions

• have a guard step that waits for the database data to be present (need to give the user something to do
• deal with each case as it comes up eg.
  • [x] waiting indicator for avatar and profile UI
  • [ ] either don't allow conversation creation until ready or allow but wait in first step until db data is present

Test

• [ ] create a conversation before user data is present in db (at /users/{userId}/...)

Additional context

140 switched from using the FirebaseAuth object for user details to using a db entry