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

[libcontacts] Ensure cache is instantiated before resolution attempt. Contributes to MER#1545



See merge request !3

[libcontacts] Ensure timestamps use C locale. Contributes to MER#1536

Timestamps must be generated using the C locale, so they do not contain
digits other than Latin.

See merge request !2

Timestamps must be generated using the C locale, so they do not contain
digits other than Latin.

[libcontacts] Provide decomposeDisplayLabel() function. Contributes to MER#1379



See merge request !1

Some data sources provide a display label (or formatted name) but not
structured name data.  The qtcontacts-sqlite backend uses structured
name data to perform aggregation, and thus it is useful to have the
decomposition function provided for clients (e.g., sync plugins).

Contributes to MER#1379

[libcontacts] Do not start timers during application close. Contributes to MER#1267

[libcontacts] Report invalid addresses as unknown. Contributes to MER#1260

An invalid address should result in a resolution-to-no-contact event.

Improve address resolution behavior

Otherwise, existing resolutions may not be updated by the addition of
better matches.

[libcontacts] Adjust fetch hint for non-completing address resolution.  Contributes to MER#1174

When resolving an address that does not need the whole contact to
be retrieved, the fetch should include any resolvable addresses of
the contact, since address resolution is obviously in use in the
caller application.

[libcontacts] Correctly initialize status flags. Contributes to MER#1206

[libcontacts] Fix unit tests

Commit 813eafc0 changed how formatted
name (FN) properties from vCards are imported, so that now an import
involving de-duplication can result in a single contact with multiple
nicknames (setNickname() actually adds nicknames if the new nickname
does not match a previously set nickname).