ksharedconfig_in_global_object.cpp is now in kdelibs4 too
(where it works) and reproduces Albert's KgDifficulty testcase.

CHANGELOG: fix assert when using KSharedConfig in a global object destructor.
REVIEW: 122232

Add new variable to specify it in *.kcfgc : "CategoryLoggingName"

CHANGELOG: Allow to generate file with qloggingcategories support.

REVIEW: 122931

This reverts commit 9eee15917e01a89d937d1cba2eebbe9d65daeb72.  As agreed
with David Faure, we are going to leave this change in place for 5.7 and
see what happens.

CCMAIL: faure@kde.org
CHANGELOG: Reverts previous commit, both can be left out of the changelog.

On further reflection, introducing a SIC to fix the bug is not ideal.  I'm
working on something that will address the underlying bug, but I didn't have
it in time for 5.7.

The versioning behaviour is left, as I do want it to exist for the future.
This only reverts the mandatory versioning of files to avoid the compatibility
break.

CHANGELOG: Undo 915976c123, which never saw a release, enough to avoid the SIC.

REVIEW: 121838
Acked by Matthew Dawson

This patch is necessary because:
When we use kf5 + kde4 application, kconf_update which launchs at the start when we launch kde.
But it will migrate some config file, for example it will show that we need to migrate konversation
so it will create a konversationrc in .config/

But when we launch konversation there is a kdelibs4migrator which wants to migrate settings and config in .config
but it shows a konversationrc in .config so it will never migrate and we will lose all settings.

So we can force to remove all .upd in kf5 but it will not fix problem during migration or when we have kde4 application
install in same directory as kf5.

So now I force for each upd file to have a "Version=5" so kconf_update (kf5) will migrate just kf5 upd file and it will fix my bugs.

REVIEW: 121797
CHANGELOG: Now kconf_update doesn't process upd file from kde4. We need to add "Version=5" in top of the upd file otherwise it will be skipped.

gcc 4.5 doesn't have nullptr.

Previously the warning "Invalid escape sequence "\;"." would appear and
"\;" was replaced with just the backslash as is done for all
unrecognized escape sequences. Keep both characters so that
readXdgListEntry() works with values containing semicolons

REVIEW: 119074