Update Table: User | Model | API | Test cases

[Ruchitha12]

Fixes #601

What changes did you make?

• Updated fields in the User model https://github.com/Ruchitha12/peopledepot/blob/d55d2e9c0b0751e745bbf1e9de2d7a909d98acc5/app/core/migrations/0053_rename_job_title_current_intake_user_intake_present_job_title_and_more.py#L13-L37
• Added fields to the User model https://github.com/Ruchitha12/peopledepot/blob/d55d2e9c0b0751e745bbf1e9de2d7a909d98acc5/app/core/migrations/0053_rename_job_title_current_intake_user_intake_present_job_title_and_more.py#L43-L52
• Note: some fields already had the desired names and types
• Updated the User API serializer
• Generated and documented the updated core_user table schema.

Why did you make the changes (we will use this info to test)?

• To align the User model with the updated intake schema requirements.

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

• No UI, only backend changes

[fyliu]

I rebased to main and updated the migration file numbering, making sure tests and linters are passing. I haven't looked at the code yet.

[fyliu]

Thanks for working on this! I think we need some clarification on the requirements for this to be sure. I will bring it up at the meeting.

[fyliu]

• made changes according to current requirements
• merged migrations
• rebased to main

[egcuriel]

Everything looks good, the changes reflect the updated requirements. Should these changes be incorporated into PRs waiting to be merged/Issues currently open, or should this PR include any changes those PRs have incorporated/Issues currently open?

[fyliu]

@egcuriel I think it's fine if PRs end up conflicting with one another. If the PR was worked on for a long time, it should be rebased to the latest main code or something recent, just to make sure the changes don't break any recent code.