Matching service occasionally returns wrong room number for both users

[Singa-pirate]

There are 2 different room numbers in MatchRecord
When a match is found, it occasionally return the wrong one that is not used in the session

[Singa-pirate]

Cause:
In matching service, the roomNumber and questionId are returned when match is found ("matched" event). This uses the data from the user who starts matching later.

io.to(socketId).emit("matched", {
  matchedWith: existingMatch.userId,
  roomNumber,
  questionId: question?.questionId,
});
io.to(existingMatch.socketId).emit("matched", {
  matchedWith: userId,
  roomNumber,
  questionId: question?.questionId,
});

When match is confirmed (""match_success") event, the roomNumber and questionId for the session is from the user who accepts the match earlier.

await prisma.sessionHistory.create({
  data: {
    roomNumber: matchedRecord.roomNumber,
    questionId: matchedRecord.questionId ?? userRecord.questionId ?? 0,
    isOngoing: true,
    userOneId: userRecord.userId,
    userTwoId: matchedRecord.userId,
  },
});

When these two users don't match, the roomNumber used is wrong.

[Singa-pirate]

Closes with #40