This issue seems to occur due to this: If a library has email as a mandatory field in the system preference, PatronSelfModificationMandatoryField

If a patron logs into their account, has an email attached to their account and tries to update any information (except for email)- they will receive an error saying that the email already exists in the database. 

Test Plan:
1. Log into Patron Account
2. Go to Patron Details
3 Ensure test patron has an email on their account
4. Change or update  or add a new data field, phone, address, etc.
5. Receive an error that states the email already exists in the database. 

If a library does not have email as mandatory if the sys pref stated above, this issue does not exist.