Case Sensitivity for Duplicate Detection for add method when it comes to adding a new person

[acekhoon]

Description: From what has tested so far, the duplicate detection is done via the name of the person since adding person named John Doe is not allowed. However, since "John Doe" and "john doe" are likely to be the same person (since they share the exactly identical address, email address and phone number), I believe that the product should identify them as a same person. This can be referred to this paragraph from PE website:

"Bugs related to duplicate detection: Duplicate detection (e.g., detecting if two persons in the address book are the same) is not trivial; often, detecting only the exact string/value matches is not enough. For example, John Doe and john doe are likely to be the same person. Similarly, extra white space (e.g., the user typed an extra space between the two names) is unlikely to mean they are two different persons. Typically, it is best if you can give a warning in such near match cases so that the user can make the final decision."

Stepts to Reproduce: Typed in "add n/John Doe p/98765432 e/johnd@example.com a/6 Sin Ming #01-01" to add John Doe, and added another John Doe by typing in "add n/john doe p/98765432 e/johnd@example.com a/6 Sin Ming #01-01"

Expected: This person is already exists in the addressbook

Actual: New person added: john doe; Phone: 98765432; Email: johnd@example.com; Address: 6 Sin Ming #01-01; Roles: ; CCA: ; Amount: 0.0; Attendance: 0/0; Metadata: //NO METADATA//

[soc-pe-bot]

Your response not required for this bug as the team has accepted the bug as it is.