BUG: 444550

(cherry picked from commit b4f6f86e)

Those should only be merged for unbound tickets, two bound tickets for
this case don't need to be the same.

Similar to the UIC company code we'll be able to use this to select
matching KPublicTransport backends for a given train ticket.

In some cases Eventbrite is putting in a single string rather than
a full place object it seems.

This duplicates a bit of code we can remove again once we depend
unconditionally on KF 5.88. Doing this now already however allows
for an easy side-by-side comparison of the results.

There are minor changes in places with ambiguous timezones, and
since country lookup is no longer tied to timezones, we now also
get proper results for Thailand and northern Vietnam.

This should now allow switching out the implementation without having to
touch the consumers, and there's no remaining use of implementation
details on the outside.

Allows us to drop yet another function we wont need with KI18nLocalData
from the interface.

Another step towards porting to KI18nLocaleData.

This is unnecessarily restrictive.

timezoneForLocation() handles that just fine.

This reduces leaking the internal timezone enum out of the knowledge db
code, which helps with the port to KI18nLocaleData.

This is meanwhile done more generically in the post-processing code.

The reasons this was optional were the early Android build and the static
extractor build for Nextcloud, both of which long since have OpenSSL as
well.

This happens when for example details about adult/child tickets end up
being part of the name.

Kai Uwe Broulik authored Oct 08, 2021 and Volker Krause committed Oct 13, 2021

Otherwise timezone information is lost

With the port of KContact to KI18nLocalData we need this in order for the
country name detection to work properly.