Add a phone number column to the user_accounts table

[plunkettgoogle]

Add a phone number column to the user_accounts table.

Description

This change adds a phone number to the user_account table, adds the corresponding migration, and updates the swagger API.

How Can This Be Tested/Reviewed?

0. Start a local server via yarn dev:all.
1. Go to http://localhost:3100/docs and use the auth/login endpoint to log in as one of the test accounts.
2. Use the auth token to set the bearer token for subsequent requests (click the lil' "lock" icon, and paste the auth token)
3. GET the user JSON through the user endpoint
4. Paste the user JSON into the request body of the PUT user/{id} endpoint, and modify the phone number field
5. GET the user JSON again through the user endpoint, and verify the phone number was set.

To run the added test:
cd backend/core && yarn test:e2e:local --testPathPattern user.e2e-spec --testNamePattern "modify their phone number"

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• I have exported any new pieces added to ui-components
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

👷 Deploy request for dev-partners-bloom pending review.
Visit the deploys page to approve it

🔨 Explore the source changes: c6ce525

[netlify]

👷 Deploy request for dev-bloom pending review.
Visit the deploys page to approve it

🔨 Explore the source changes: c6ce525

[netlify]

✔️ Deploy Preview for dev-storybook-bloom ready!

🔨 Explore the source changes: c6ce525

🔍 Inspect the deploy log: https://app.netlify.com/sites/dev-storybook-bloom/deploys/617888f148d98c00088e04af

😎 Browse the preview: https://deploy-preview-2075--dev-storybook-bloom.netlify.app

[plunkettgoogle]

Apologies, the test I added is not passing (it was passing in the downstream project). I'll address that soon.

[plunkettgoogle]

Ah, actually I see that the /user/:id endpoint is admin only after #1862, which has not yet landed in the downstream CityOfDetroit project. I'll close this, and reopen another PR once we've pulled in those changes.