[buteo-sync-plugins-social] Fix bugs in Google Contact sync. Contributes to JB#51541

See merge request !71

When upsyncing contacts, the server will reply with an updated etag
for each contact in postFinishedHandler(). Save the etags to their
contacts before calling localChangesStoredRemotely(), which will save
the updated contacts to the database. Also save the avatars at this
point instead of in finalize(), as calling QContactManager::saveContacts()
will flag the contacts as modified and cause spurious modification
detections on the next upsync.

Also:
- Ensure the correct detail is looked up for the etag data
- Don't remove contacts from the localAdded/Modified lists in
batchRemoteChanges(), because these lists are then passed onto
localChangesStoredRemotely() for saving
- Save the last sync time in finalize() so that it is not saved if the
sync failed.

Encode and decode the gd:fullName entry in the atom feed. The server
always sends a fullName composed from the first name, last name,
prefix etc. so encoding this in the request will avoid a spurious
modification from the server on the next sync after it reassembles the
fullName on the server side.

We no longer hardcode the name of the default My Contacts collection,
so when searching for it we cannot look for the hardcoded name.
Instead, mark the collection with a special piece of metadata.

Also fix a bug in etag detection.

Finally, ensure we ignore detail access constraints when updating
detail data during sync.

[buteo-sync-plugins-social] Remove ssu dependency. Contributes to JB#38781

See merge request !70

Doesn't seem needed anymore. Commit 13e017fe removed the only need(?)

Ensure Google Calendar allDay flag is set correctly

See merge request !69

[buteo-sync-plugins-social] Ensure Google Calendar allDay flag is set correctly. Contributes to JB#51406

Ensures that the "allDay" flag for an event is set in the case where the
start date is a date only (no time) and one of the following holds:

1. The start date and end date are the same (single day event).
2. The end date is one day after the start date (single day event).
3. Anything else (multi-day event).

In the case of 3, the end date is adjusted to account for the fact that
allDay events have exclusive, rather than inclusive, end dates.

Google address book name should come from the atom feed, instead of
being hardcoded.

Jb50552 qtpim upgrade

See merge request !66

- Use fetchCollections() instead of QContactManager::collections() when
purging to ensure deleted collections are searched
- Store unsupported elements data per-contact instead of per-collection
- Use QContactExtendedDetail instead of QContactOriginMetadata for etags
- Purge per-account in KnownContactsSyncer

It will not work with the latest QtPim changes, and as it's unused it
should be removed anyway.

- Update the contact avatar when it is modified or removed on the
server, rather than only when it is added.
- Remove avatar files for deleted accounts.

[buteo-sync-plugins-social] Don't use custom qtcontacts-sqlite extension values that already exist in latest QtPim. JB#50552

- Implement the TwoWayContactSyncAdaptor interface
- Remove OOB usage (no longer necessary to store data out-of-band
- No longer needs to determine contact deltas when syncing. This is
done by TwoWayContactSyncAdaptor instead.
- Fix avatar download url
- Use a VK collection specific to the account, instead of a sync target
- Remove old clean-up code path for stale contact avatars

- Implement the TwoWayContactSyncAdaptor interface
- Instead of using sync targets, create per-account contact
collections

- Implement the TwoWayContactSyncAdaptor interface
- Remove OOB usage (no longer necessary to store data out-of-band)
- Use a collection specific to the account, instead of a sync target
- Remove old clean-up code path for stale contact avatars

Notifications

See merge request !62

Notification previews are now shown by default, so explicitly disable
them as per existing behavior.

Remove category files that are only used from one code source and
define the metadata in the source instead, unless a category file is
required to set custom hints for QML-only notifications.

VK-related conf files are not used and can be removed.

[buteo-sync-plugins-social] Remove uses of x-nemo-priority hint for non-lock-screen notifications. JB#50446

[buteo-sync-plugins-social] Save sync profile name to notebook.

See merge request !58

[buteo-sync-plugins-social] Updated kcalcore exports exclusive dtEnd. Contributes to JB#47814

See merge request !50

Signed-off-by: Matti Kosola <matti.kosola@jolla.com>

[aarch64] Do not hardcode lib dir. Contributes to JB#50028

See merge request !59

[buteo-sync-plugins-social] Don't pass oauth token as key query parameter. Contributes to JB#50140

See merge request !61

Google calendar sync recently started (intermittently) failing.
I believe the reason is that for some API endpoints, Google now
requires an API specific key to be passed as a query parameter,
aside from the oauth2 token which is passed in the authorization
header.  Even though the Calendar API is not one of the APIs which
requires this type of API key, passing the oauth2 token as a key
parameter was causing issues.

This commit ensures we don't pass the token as a query parameter.
It is already provided in the authorization header.

[buteo-sync-plugins-social] Set the default backup time to 2:00. JB#49819

See merge request !60