[User Registration] Make email required on backend

[lpatmo]

Context

We need to make sure the email field is required when a new user is registered via the /auth/users API endpoint.

Acceptance Criteria

[ ] Change the line in the model to make sure email is required
[ ] Make migrations file and run migrations
[ ] Add models test
[ ] Make sure tests pass

Ticket sizing

1 (small)

[BethanyG]

@lpatmo This is not an API change and since we are using a custom model, it is an addition (I keep forgetting that too!)

Add email in users_user as a required (non-blank) field.

Since we are using a custom user model, this change will need to be made in the model.py file of the users app.

• Custom User Models (Django Docs)
• Referencing the Custom User Model (Django Docs)
• Considerations for a Custom User Model
• Related SO Post on Requiring Email for Custom User Model

[lpatmo]

Gah I was going to give this to @bkbuilt or someone else who expressed interest since it's a good beginner issue, but started playing around to test it out in a new branch and realized I might as well create a PR for it.

PR: https://github.com/chris48s/backend/pull/1/files

Note that it is based off of #109.

I documented my implementation steps in chris48s#1, so if something drastic changes in #109 the implementation steps should be easily re-created.

[lpatmo]

(Or... if #109 gets merged in first, I'll just re-submit the PR to point towards master instead of towards Chris' branch)

[BethanyG]

@lpatmo I hate to do this to you, but for clarities sake, I really think this should be a separate PR...just so we keep related PRs with their milestones??

[lpatmo]

No problem, I meant to do this as a separate PR, but realized this was dependent on the other PR being merged in 😅. Happy to resubmit the PR to master after that other PR is resolved!

[BethanyG]

🤔 ...yeah. We need to get our arses in gear around testing....aaaaand you'll need to add a model test for your change 😄 .

[lpatmo]

Haha, cool! I missed that in my acceptance criteria 😅