Sqservices 1028 be add sso SCIM attributes to user profile for team admins unvalidated email

[battermann]

as a team admin
when I search for team contacts in team management
I want to see un-validated emails in the user profiles that are returned by the search

https://wearezeta.atlassian.net/browse/SQSERVICES-1028

Checklist

• The PR Title explains the impact of the change.
• The PR description provides context as to why the change should occur and what the code contributes to that effect. This could also be a link to a JIRA ticket or a Github issue, if there is one.
• If this PR changes development workflow or dependencies, they have been A) automated and B) documented under docs/developer/. All efforts have been taken to minimize development setup breakage or slowdown for co-workers.
• If a cassandra schema migration has been added, I ran make git-add-cassandra-schema to update the cassandra schema documentation.
• changelog.d contains the following bits of information (details):
  • A file with the changelog entry in one or more suitable sub-sections. The sub-sections are marked by directories inside changelog.d.

[fisx]

also good... mostly. :)

feel free to second-guess me if you can make @smatting agree with you!

[fisx]

Is this type only visible to admins? If not, hiding the unvalidated email should be enforced:

data TeamContact f = TeamContact
  { ...
    teamContactEmailUnvalidated :: f Email
  }

...
userSearch :: ... -> m (TeamContact (Const ()))
...
adminSearch :: ... -> m (TeamContact Id)
...

[battermann]

AFAICT this type is only visible to team admins. It already contains potentially confidential data.
see: https://github.com/wireapp/wire-server/blob/develop/services/brig/src/Brig/User/API/Search.hs#L234

[fisx]

given that changing this column and changing other columns usually don't coincided (or do they?), wouldn't it be more straight-forward and more readable to have new table?

[battermann]

there is one big advantage when having it in a single table, and that is we only have to query C* once when creating/updating the ES index.
if you insist, I'm also ok with having a new table.

[smatting]

Can you please bumpt expectedMigrationVersion to trigger a reindexing?
Also please update oldMapping in the brig integration tests.