[INTF25] Build flag applicant mutator

[ericahan22]

Notion ticket link

Build Flag Applicant Mutator

Implementation description

• Added isApplicantFlagged to ApplicantRecordDTO
  • Also changed type of id from number to string to comply with the Technical Design Document and database schemas
• Added the service function setApplicantRecordFlag to set it to true/false
• Made relevant resolver file with setApplicantRecordFlag mutator
• Added applicantRecordType to the GraphQL types
  • Used String! types for position and status columns instead of enums
• Created a migration to add createdAt and updatedAt columns to the applicant_records table

Steps to test

1. Run the following mutation in the GraphQL playground and ensure it works. Instead of rec_123 use a real applicantRecordId, e.g., aa6cb234-ecc5-43e5-b2cf-4ec426577658. Try with flagValue as true and false.

mutation {
  setApplicantRecordFlag(applicantRecordId: "rec_123", flagValue: true) {
    id,
    applicantId,
    position,
    roleSpecificQuestions,
    choice,
    status,
    skillCategory,
  }
}

2. To see the effect of setting the applicant flag, also try

mutation {
  setApplicantRecordFlag(applicantRecordId: "rec_123", flagValue: true) {
    id
    applicantId
    position
    roleSpecificQuestions
    choice
    status
    skillCategory
    combined_score
    isApplicantFlagged
  }
}

What should reviewers focus on?

• Make sure design justifications are reasonable
• Make sure the migration file is ok

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

[mxc-maggiechen]

LGTM!

[isabellehuangg]

👍 Makes sense