Integrate miscellaneous features for collaboration feature

[bensohh]

This PR summarises the additional implementation added to the existing collaboration feature

Things Done:

• Changed the session's Matched User to pull from the WebRTC's provider instead of localStorage (it will display Loading... until the onChange event occurs, might take some time to load)
• Implemented a count-up stopwatch for the collaboration session and its handler to stop the stopwatch when the session end button is triggered (Currently utilising localstorage)
• Wrapped the existing end session button within a Modal Component to double-check if user intends to end session
• Implement the end session for both users:
  • When user1 and user2 are matched into a collaboration session, either user that triggers an end session will result in the session being ended for both users (as discussed/agreed on previously, we can change this if we want)
  • Example flow: user1 triggers end session --> sets a endSession state in the provider to inform user2 --> user2 listens for change event in states and detects a change in the states --> user2 realise its an endSession --> triggers end session for user2 --> Notification Displayed --> End Session Modal shown --> redirected to matching page
• Minor fixes: changed the <text> component that has been throwing error to <span>

Additional TODO (to be discussed):

• Storing of timer in db instead of localStorage
• Detection of close window/tab for collaboration session to trigger end session
• Selection of language for collaboration editor (Nice to have?)
• Test-cases and execution service

Noticed unintended behaviour:

• After submission of code, display notifications (for both user and peer), trigger end session, displays code submission notification for peer again @solomonng2001

[solomonng2001]

LGTM