31 February is allowed as a meeting date

[jialatteo]

addM l/007 n/Joke Peralta d/2022-02-31 12:00 is allowed even though 31 February does not exist.

Success message after executing the command is shown below:

[nus-se-script]

Team's Response

A severity of low seems more appropriate here as a user inputting a date of 30th February is unlikely, and if done so does not affect usage of the product greatly.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

• [x] I disagree

Reason for disagreement: The application should at least give a warning message or block this command.
The application also does not check for meeting clashes.

In the scenario that:

• user has ~100 meetings scheduled and does not MANUALLY check for the meeting clashes
• user has another meeting scheduled on the 2022-02-28, 12:00 OR user actually thinks 2022-02-31,12:00 exists
  
  this bug can cause the user to miss out on a client.

---