[INTW26] Implement backend updates for interview scheduling feature

[chene0]

THIS BRANCH IS CURRENTLY BASED OFF OF INTW26-build-interview-delegation-algorithm, REBASE ONTO MAIN ONCE #127 GETS MERGED

Notion ticket link

Implement Interview Scheduling Feature

Implementation description

• In the model User, add a fk profilePictureFileId to firebase_files
• Define and implement new resolvers getInterviewedApplicantsByGroupId and getInterviewersByGroupId for the interview review page

Steps to test

1. docker compose up and docker exec recruitment_tools_backend node migrate up, ensure that the migrations ran successfully and in pgAdmin the users table now has a profilePictureFileId fk to firebase_files
2. Run the following sql queries separately and in order to create copies of each existing seeded applicant record

CREATE EXTENSION IF NOT EXISTS pgcrypto;

INSERT INTO public.interviewed_applicant_records (id, "applicantRecordId", status, "createdAt", "updatedAt")
SELECT
	gen_random_uuid(),
	id,
	'NeedsReview',
	NOW(),
	NOW()
FROM public.applicant_records
ON CONFLICT ("applicantRecordId") DO NOTHING;

3. Run the following sql query to create a bunch of dummy users with position "Developer"

INSERT INTO users (first_name, last_name, email, auth_id, role, position, "isActive")
VALUES
  ('Test', 'User1',  'testuser1@test.com',  'test_auth_1',  'User', 'Developer', true),
  ('Test', 'User2',  'testuser2@test.com',  'test_auth_2',  'User', 'Developer', true),
  ('Test', 'User3',  'testuser3@test.com',  'test_auth_3',  'User', 'Developer', true),
  ('Test', 'User4',  'testuser4@test.com',  'test_auth_4',  'User', 'Developer', true),
  ('Test', 'User5',  'testuser5@test.com',  'test_auth_5',  'User', 'Developer', true),
  ('Test', 'User6',  'testuser6@test.com',  'test_auth_6',  'User', 'Developer', true),
  ('Test', 'User7',  'testuser7@test.com',  'test_auth_7',  'User', 'Developer', true),
  ('Test', 'User8',  'testuser8@test.com',  'test_auth_8',  'User', 'Developer', true),
  ('Test', 'User9',  'testuser9@test.com',  'test_auth_9',  'User', 'Developer', true),
  ('Test', 'User10', 'testuser10@test.com', 'test_auth_10', 'User', 'Developer', true),
  ('Test', 'User11', 'testuser11@test.com', 'test_auth_11', 'User', 'Developer', true);

4. Run the following mutator, copy any one of the returned groupId in the response

mutation DelegateInterviewers {
    delegateInterviewers(positions: ["Developer", "VP Engineering"]) {
        interviewedApplicantRecordId
        interviewerId
        interviewHasConflict
        groupId
    }
}

5. Call the following queries and confirm they work with the copied group id

query GetInterviewedApplicantsByGroupId {
    getInterviewedApplicantsByGroupId(
        groupId: "<copied group id>"
    ) {
        applicantRecordId
        firstName
        lastName
    }
}

query GetInterviewersByGroupId {
    getInterviewersByGroupId(groupId: "<copied group id>") {
        id
        firstName
        lastName
        email
        role
        position
        profilePictureFileId
    }
}

What should reviewers focus on?

• Queries return error response for group ids with invalid uuid syntax

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[chene0]

added this BelongsTo decorator so i could do joins for getInterviewedApplicantsByGroupId

[mxc-maggiechen]

idk if there is a better way to dedupe this

[mxc-maggiechen]

update is required for the scheduling PR, create and delete are added as well bc it's just nice to have CRUD on a model all set