Add bulk import users from emails

[victorhuangwq]

Description

Adds ability to create users from bulk using just email.

Adds:

• UI to add emails and assigned role in bulk
• Frontend validation
• Validation, creation of account (if doesn't exist), and assigning of roles

Motivation and Context

Creating accounts individually for adding CAs and Instructors is tedious for class with of them (~40).

How Has This Been Tested?

Tested Valid Inputs:

• Single entry: dave@autolab.com (should be added/updated with new role), assigned as instructor
• Multiple line of entries: dave1@autolab.com, greg@autolab.com, assigned as course assistant
• Multiple lines of mixed entries: dave@autolab1.com, Greg <greg1@autolab.com>(first name / last name should be updated accordingly), assigned as student
• Mix of pre-existing & new users: Dave <dave@autolab.com>, Greg <greg@autolab.com>, assigned as instructor (We see that we do not update the pre-existing user's name, just the role)

Tested Invalid Inputs:

• Single entry: dave, assigned as instructor (error message of invalid email)
• Single entry: dave@test.com, no assigned role (error message of assigned role)
• All wrong entries: dave, test@@.com, greg, dave <test@g (shows which entries are wrong)
• Mix of correct and wrong: dave, dave@test.com, greg (shows which entries are wrong)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have run rubocop for style check. If you haven't, run overcommit --install && overcommit --sign to use pre-commit hook for linting
• My change requires a change to the documentation, which is located at Autolab Docs
• I have updated the documentation accordingly, included in this PR

Other issues / help required

If unsure, feel free to submit first and we'll help you along.

[victorhuangwq]

@michellexliu Since you worked with roster upload, before I continue further, could you take a quick look at the logic below?

[damianhxy]

For the first invalid input, I get a different error message

[damianhxy]

Functionality works as expected, but left some comments.

As an additional nit, I realized that I can't press arrow up / down in the text area -- not sure if that was intended.

[damianhxy]

Thanks for addressing the comments

Other than a comment about error message consistency, LGTM!

[victorhuangwq]

Tested with:
firstName <firstname@name.com>
firstName lastName <firstlastname@name.com>
firstName M lastName <firstmlastname@name.com>

[victorhuangwq]

@damianhxy do a last check review on the cases above. Thanks!

[damianhxy]

Tested cases as working.

However, it's a bit weird that we're ignoring middle names altogether. Should we lump it with first names?

[victorhuangwq]

Currently the roster upload doesn't support middle name as well. So I think it's logical to just drop the middle name to be consistent.