[contacts] Backport notification changes to 3.4.0. Contributes to JB#51257

See merge request !21

[libcontacts] Avoid crash from null ContactManagerEngine

See merge request mer-core/libcontacts!19

Use macros, not hardcoded paths.

See merge request mer-core/libcontacts!18

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

More robust phone number matching using libphonenumber

See merge request mer-core/libcontacts!15

This commit yields a significant improvement to how our phone number
matching works. It gets rid of a lot of false positive matches.

Previously we used a "minimized" number which we stored in the cache
and used for matching. This lead to false positives between numbers
for which the "minimized" number was the same when the full wasn't,
for example when the area code of the number differs in only one digit.

Examples of solved false positive matches:
"+36 20 123 4567" and "+36 30 123 4567" were matched incorrectly.
"+36 20 123 4567" and "+44 20 123 4567" were matched incorrectly.

The new approach is to cache the full phone number and perform the
matching between the full numbers using libphonenumber, which has
a quite resilient algorithm for this. Local numbers and
international direct dial (IDD) are still matched:

Examples of local and IDD numbers that still work:
"+36 20 123 4567" still matches "06 20 123 4567" (local)
"+36 20 123 4567" still matches "00 36 70 381 0581" (IID)

Limitations:
We currently do NOT pass a default region code to libphonenumber,
which means that some false positives can still occour in edge
cases when a country code would be required to distinguish between
the two numbers. This only happens when some numbers are supplied
in a non-international format.

Examples of remaining false positives:
"06 20 123 4567" is a false positive match of "+1 0620 123 4567"
"00 36 20 123 4567" is a false positive match of "+1 00 36 20 123 4567"

We deem that the remaining false positives are unlikely enough that
they don't matter in practice. If this becomes relevant, we will need
to make it possible to pass a region code to the matching algorithm.

[libcontacts] Filter out false positive matches even if there is only one query result. Contributes to JB#38835

[libcontacts] Allow caching filter match role. Contributes to JB#47217

See merge request mer-core/libcontacts!17

This is the role whose data matched the filter pattern.

[libcontacts] Update section bucket index cache after deletions. Contributes to JB#46496

See merge request mer-core/libcontacts!14

When a contact is deleted, we need to recalculate the section bucket
index cache as that contact may have been the only contact in a given
section bucket (display label group).

However, since updating the section bucket index cache is an expensive
operation, we should only do this once per bulk deletion, so this
commit also adds support for bulk deletion operations.

[libcontacts] Emit saveContactComplete() when appropriate. Contributes to JB#45633

See merge request mer-core/libcontacts!13

When a new contact is created via a save operation, the backend will
create that local constituent and also an aggregate for it.
The UI often wants to know that newly created aggregate's ID, e.g.
to show the contact card.

[libcontacts] Also update section bucket index cache during list synchronisation. Contributes to JB#45836

See merge request mer-core/libcontacts!12

[libcontacts] Also update section bucket index cache during list synchronisation. Contributes to JB#45836

Batch updates are handled via list synchronisation.  We need to
ensure that we update the section bucket index cache of any model
after a list synchronisation occurs.

And remove blts-tools dependency as that is no longer available

[libcontacts] Explicitly tell models to update section bucket index caches. Contributes to JB#45504

See merge request mer-core/libcontacts!11

When contact data changes in the backend and we have pulled these
changes into the model, we need to tell the attached models that
they need to recalculate their cache of section bucket indexes.

Note that we cannot have a single cache of section bucket indexes
which the models read, as models can have a search filter applied
which means the indexes of contacts in the seaside cache won't
necessarily match what the model expects.

Remove dead code

See merge request mer-core/libcontacts!9

[libcontacts] Force models to reload data upon receiving dataChanged. Contributes to JB#44742

See merge request mer-core/libcontacts!10

The qtcontacts-sqlite backend will emit dataChanged() when the
group property changes and it updates its internal data structures
accordingly.

This commit ensures that when this signal is received by libcontacts,
it will force all models to update all source data, to ensure that
the group labels are updated appropriately.

And increase version of qtcontacts-sqlite-extensions dependency

[libcontacts] Replace name group with display label group. Contributes to JB#44742

See merge request mer-core/libcontacts!8

Fix recursive resolve

See merge request mer-core/libcontacts!6

ResolveListener::addressResolved() implementations can do silly things
like start resolving for something it just received information for.
That ended up new request being filtered out as duplicate request
but then never getting response with addressResolved.

Above case with libcommhistory / RecentContactsModel.

[libcontacts] Fix defines from public header. Contributes to JB#39107

See merge request !5

[libcontacts] Load decomposition translations. Contributes to MER#1664

Previously, we relied on the client application to load the translation
files prior to performing FN to N decomposition tokenisation.
This commit ensures that the translations are loaded by libcontacts.

Contributes to MER#1664

See merge request !4

Previously, we relied on the client application to load the translation
files prior to performing FN to N decomposition tokenisation.
This commit ensures that the translations are loaded by libcontacts.

Contributes to MER#1664