fix: prevent insertion of duplicate phone numbers when calling updateContact

[aconanlai]

This fixes the issue where we'd see vCards with multiple identical phone numbers for the same contact (sometimes formatted differently, e.g. with +1).

I've traced the error back to react-native-contacts creating new phone number entries in the database.
The issue has been solved but we forked react-native-contacts in early 2019 and haven't rebased/merged since then. Relevant github issue:
morenoh149#332

The tl:dr is: previously, updateContact would expect the phone number entries to have the id attached to it so it could update that number - without an id, it would insert a new row instead. Since updateContact expects the entire contact to be passed in as an argument, contributors found that a good solution was to delete all existing numbers and then insert the new number.

This PR patches the updateContact method with these change.

To test: you can confirm the behaviour of this bug currently by adding logs before the updateContact call in react-native in LightOS (in src/lib/LightOS/Contacts.js), as well as logging the response (the library responds with the updated contact). You can see before and after editing a contact (you don't have to even make any changes, a call to updateContact will cause the bug) that the vcard exported from the dash will have an extra TEL entry. As well, the response to updateContact will show the duplicate row(s).
Then, you can rm -rf node_modules, update the branch specified in package.json from lightos to fix/number-upsert, yarn install, clear the build cache and rebuild. Upon running the same tests, you'll see that the contact always only has 1 number in the vcard and in the response from react-native-contacts.

[breannamporter]

LGTM