Sync OAuth Primary Email to d_b_users Table

[jimmybrancaccio]

Is your feature request related to a problem? Please describe

When working with customers in support there are time when I want to verify them by searching the email address that submitted the support ticket with what we have in our database (to ensure they match). However there are times when a customer updates their primary email address at their SCM. This causes the value store in the d_b_users table to become "de-synched".

Describe the behaviour you'd like

If the customer does change their primary email address at their SCM we should pull in that update so that it matches what we store and use when searching by email address at /admin/users.

Describe alternatives you've considered

Ask the user to recreate the ticket for the appropriate email address. This doesn't always work as they may no longer have access to the original email address as an example.

Additional context

N/A

Front conversations

[AlexTugarev]

@jimmybrancaccio, I think we need to clarify on this one. Now, we have a User.email attribute which one can manage on https://gitpod.io/account manually, and this one should be used for communications etc. primarily.

Then there is a primary email address fetched from each SCM provider per identity, which should be used to create commits with. At this point there is a gap with private email addresses, so ideally it should be a set of of email addresses per provider.

Anyways, I don't think syncing the email addresses is the right way, because it would lead to more confusion when dealing with multiple SCM provider connections.

[jimmybrancaccio]

Whatever the answer is, I would like to be able to look up a customer in the Gitpod admin UI using the email address they created their support ticket with and compare it with a "known good" email address (likely the primary email address of their primary SCM) of their Gitpod account.