Better null checking

[jmgasper]

From the October challenge 1 review:

#77 Bug mentions for backend

In addition to tracking the copilot in the UI and DB, we also need to ensure that the configured value is used when creating tickets. Please ensure that when the copilot is set, it is using the configured copilot handle from the DB, not the owner of the project.

You change

async function getExistingChallengeIdIfExists(event, dbPayment) {
  // check if there is existing active challenge associated with this project
  const existingPayments = await CopilotPayment.findOne({
    project: dbPayment.project,
    username: event.data.copilot.handle,

to

async function getExistingChallengeIdIfExists(event, dbPayment) {
  // check if there is existing active challenge associated with this project
  const existingPayments = await CopilotPayment.findOne({
    project: dbPayment.project,
    username: event.project.copilot,

You should be first checking if copilot is null or not

Same issue as above in this method too

async function _checkAndReSchedule(event, payment) {
  // get all unclosed payments for given project and user
  const existingPending = await CopilotPayment.find({
    project: payment.project,
    username: event.data.copilot.handle,

async function _checkAndReSchedule(event, payment) {
  // get all unclosed payments for given project and user
  const existingPending = await CopilotPayment.find({
    project: payment.project,
    username: event.project.copilot,
    closed: false,
    status: 'challenge_creation_pending'
  });