Sync: re-factor error handling

[rfc2822]

Currently, handling of sync errors is scattered between various locations:

• Sync worker throws and handles some errors and show notifications for some other errors
• Syncer throws errors (for instance when the content provider is not available, after Remove address books sync authority and content provider #877) and handles others (SecurityException, DeadObjectException)
• SyncManager throws and handles other errors (per collection)

We should

• clearly define which component is responsible for throwing which error,
• define which component is responsible for handling which error in which way (notification, instant/with retries, …)
• show a notification when the content provider can't be acquired at sync during to missing permissions or other reasons (see Remove address books sync authority and content provider #877 (review))

and refactor accordingly.

Maybe have a separate (injectable) error manager that does notifications and for instance can also group errors of various collections? But that could also be a new issue.

Depends on #877. See also #886 – it probably makes sense to think about error handling when defining the sync result data type.

Depends on #896

[github-actions]

This PR/issue depends on:

• Remove address books sync authority and content provider #877
• Generalize Syncer #896

[rfc2822]

If a collection has 404: show a message that refreshing the service list may help.