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

[buteo-sync-plugins-social] Update OneDrive sync adapters. Contributes to JB#44541

See merge request !57

Access to OneDrive content is now via the Microsoft Graph API.
This has some advantages (e.g. we can directly request thumbnail
metadata directly in picture folder / album queries).

Jb49022 service api

See merge request !56

The backup profile may now be triggered automatically via sync
schedules. When the profile is triggered, use org.sailfish.backup
to start system backup processes before uploading backup files to
the cloud service.

All backup configuration is now handled by org.sailfishos.backup,
so it's no longer necessary to read/write this config via the
sync profile.

Restrict the upload/download implementation to only transfer one
file from the local/remote directory as it's not necessary to
transfer more than one during the sync process.

Split Dropbox and OneDrive plugins into separate plugins for each of
the backup, backup-query and backup-restore features.

[buteo-sync-plugins-social] Store the owner email address as a custom property of the notebook. Contributes to JB#46575

See merge request !52

Setting notebook properties based on calendar info.

[buteo-sync-plugins-social] Store the owner email address as a custom property of the notebook. Contributes to JB#46575

For consistency with other plugins, store the owner email address
as a custom property of the notebook, for Google Calendars.

Also, make use of the custom property facility to store the
server-side calendar id, rather than abusing the plugin() field.

[buteo-sync-plugins-social] Prevent crash in Google Calendars sync plugin. Contributes to JB#47783

See merge request !55

Be overly defensive to attempt to ensure that we don't attempt to
dereference any null pointers.

[buteo-sync-plugins-social] Fix Google calendar event duplication. Contributes to JB#47783

See merge request !54

This commit ensures that if the sync token or timeMin value for a
notebook is invalid, we immediately abort sync, and then clear the
sync token stored in the notebook's custom property as well as
update the syncDate to an appropriate value.

Store created/updated timestamps appropriate to ensure that filtering
events for change or deletion since the last sync anchor works.

Fix bugs in codepaths related to partial upsync artifacts, by ensuring
that the event gcalId is calculated appropriately.

[buteo-sync-plugins-social] Discard spurious local addition due to downsync. Contributes to JB#47783

Previously, we would determine that local additions caused by a
downsync during the previous sync cycle should be treated as
local modifications, and upsynced.

This commit checks whether a local modification has indeed occurred
by checking the lastModified date stamp, and if no modification has
occurred, discarding the change to prevent spurious upsync.

It also fixes a bug where the wrong "since" date time would be used
when determining the local changeset, as it may be using one from
a different notebook by mistake.  This commit updates the code so
that the appropriate previous sync date for the specific notebook
is used.

[buteo-sync-plugins-social] Discard spurious local modification due to remote organizer change. Contributes to JB#47783

If a local modification is reported as a change since the last sync,
but the data in the event is identical to the data reported by the
server for that event except for the organizer email address,
then it is probably a spurious change (since Google will add the
organizer email automatically).

This commit detects that case and doesn't attempt to upsync the
modification.

Some changes (e.g. changing the organizer of an event in a shared
calendar) are not allowed, even if the user has Owner access to the
shared calendar (since the organizer field is managed specially
by Google in the shared-calendar case, allowing only the organizer
or the creator of the event to write changes there).

If we hit such a failure, ignore it and allow sync to succeed.

[buteo-sync-plugins-social] Properly store the mapping between gcalId and local UID. Contributes to JB#47783

Previously, we always stored an empty gcalId in the mapping.
This could result in "known" partial upsync artifacts being
ignored and re-upsynced, causing server-side event duplication.