Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/263

The Microsoft365 has its own handling of the backoff policy, thus
disable just added handling by the ESoupSession.

Related to https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/518

It was needed only for internal tests, but it breaks reproducible builds,
thus pass the in-tree path to the library through the environment variable,
to avoid the problem.

Related to https://gitlab.gnome.org/GNOME/evolution-ews/-/merge_requests/10

Some attachments may not have `contentBytes` property, the same as it can be
quite large file, thus read them one-by-one instead.

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/267

With help of the code from evolution-mapi to decode recurrence blobs,
read also detached and recognize deleted instances of a recurring
event series.

Be able to modify event series by either modifying single instances or
delete them.

(cherry picked from commit 6c7d57fe)

Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/2687

(cherry picked from commit 61a4bf0f)

Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/2230

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/273

The folder counts can come in any time, without the code knowing when the change
will be saved, thus schedule a timeout to save the changes, thus they are not lost.
This could be mainly visible when the unread count changes on the folder without
being saved, thus the next start the Evolution indicated new messages had been
received to the folder, even though there was no new messages at all.

The internal conversion from MIME to Json can miss some important information,
like currently for example thread references, thus rather pass the message
as a MIME blob than trying to fill related properties of a Json object.

A disadvantage is that the messages are always stored to the Sent Items folder.

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/274

The `git clone` for libcanberra is currently failing with "permission denied"
error, thus workaround it, thus the CI can run, by downloading a tarball
release instead and patching it locally.

This has been fixed as a side-effect of commit 3de4d877,
this change is only for completeness.

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/275

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/277

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/276

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/278

The EWS part can create them since https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/89 ,
thus allow to create them also for the Microsoft365 calendars.

To avoid code duplication (of the broker communication) between
the EWS and the Microsoft365 backend, this patch introduces a shared
library libevolution-ews-common. For now, only the generic parts of the
broker communication are implemented there.

Related to https://gitlab.gnome.org/GNOME/evolution-ews/-/merge_requests/11



Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>

This adds support for the OAuth2 protocol extension ms-oapxbc.
For that, we get an SSO Cookie from a locally running
microsoft-identity-broker service via D-Bus and inject that into the
OAuth2 credential prompt dialog. If no broker is running, no token
is injected.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>

Closes https://gitlab.gnome.org/GNOME/evolution-ews/-/merge_requests/11

The are functions copied from the Evolution code, to not depend on Evolution
in the backends and modules, which could bring into the random processes also
the gtk dependency, which could break when the app was not using the same
gtk version as Evolution.

This limits the code duplication at least within the evolution-ews.