feat(organizations): disable email updates for regular organization members TASK-997

[duvld]

🗒️ Checklist

1. run linter locally
2. update all related docs (API, README, inline, etc.), if any
3. draft PR with a title <type>(<scope>)<!>: <title> TASK-1234
4. tag PR: at least frontend or backend unless it's global
5. fill in the template below and delete template comments
6. review thyself: read the diff and repro the preview as written
7. open PR & confirm that CI passes
8. request reviewers, if needed
9. delete this section before merging

📣 Summary

UI for changing emails is disabled for Members of a multi-member organization.

👀 Preview steps

1. Make sure your user's email is correct in both the user section of the django admin as well as the email address section. If there is a difference it would only show the former here. See https://www.notion.so/kobotoolbox/task-1236
2. Make an MMO that has an owner, admin, and a member, as well as a regular user
3. Navigate to the account settings page
4. Visit the security section
5. If the user is a regular user, or an MMO owner or admin, they should be able to change their email address as normal
6. If the user is a member of an MMO the text box and button should be gone

📖 Description

Remove the text box and button entirely if the user is a member. Replaced with just text of the email returned from /me.

💭 Notes

Make sure the user either has the proper email reflected in the user section of the django admin or was created through an email confirmation link. See https://www.notion.so/kobotoolbox/task-1236

[notion-workspace]

Disable email updates for org members [FE]

[jamesrkiger]

Should we move this container div inside the userCanChangeEmail check?

[duvld]

This is a bit of a hack, if the container div is inside of the check then the rest of the row CSS gets unaligned. The only way I saw to fix this was to add conditional styling which I thought looked worse than this. What do you think?

[jamesrkiger]

Ah, I wondered if that might be the reason. I'd say we should go with conditional CSS. You're right that it will add some more complexity, but I think it will make it easier for other coders working on this section in the future to know what's going on.

[jamesrkiger]

@duvld There was an import error, so I pushed a fix for that. I also made a small change to simplify the logic in that cx() function. You can go ahead and merge unless you have any objections to my changes.