ContactSyncService: Implement related functions

[DaVinci9196]

Includes:

1. After adding/deleting/modifying contact groups and personnel information, the cloud and device are synchronized with each other.
2. After adding/deleting/modifying contact avatar information, the cloud and device are synchronized with each other.

Note:
Tried to use PeopleApi, but did not have access to the interface.

[Sense101]

@DaVinci9196 so can people api not be made to work with MicroG? This is critical, as since a few weeks ago all requests made to the old apis return:
Received 429 status code: Contacts API has been deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration.

This includes the google contacts sync adapter

[Sense101]

@DaVinci9196 I would like to help to finish implementing this. Please respond.

[DaVinci9196]

@DaVinci9196 I would like to help to finish implementing this. Please respond.

Sorry, I just noticed today that I used OauthToken generated based on GMS and Google Contacts app when verifying whether PeopleApi is available. Unfortunately, errors such as unable to access the API and no contacts permission appeared. You can try to see if there are other ways to solve these errors.

[Sense101]

I am looking into this

[Sense101]

I am still looking into this, as the entire structure of the api has changed this is not as simple as I thought.

[000exploit]

@Sense101 sorry for bothering, but what have you discovered?

[Sense101]

No problem, took a break from this although I will be returning to it. Part of what I was working on is that the format of the .proto files (which define data sent between the client and server) must include specific annotations to link up correctly with the new google api's. This required different dependencies to the ones used right now in MicroG, which was a whole mess to sort out.

Still lots of work to do, but that's part of what I discovered :)