With wlroots and libwayland this warning is triggered at too many places. Still
it might make sense instead to enable the warning in general and disable it in
a more targetted manner with pragmas. For now we opt for the general removal
and add a todo comment to revisit later.

Produces a lot of warnings with gcc and potentially clang on structs where we
default-initialize some fields.

Produced compile warnings.

Produced compile warnings.

Taking the distance between the pointers is wrong. A warning on the for-loop
number types indicated this issue.

The desktop numbers are unsinged, so cast to int before comparing to zero.

They were declared but not defined.

The keyboard and by that the device files are referenced in X11 too.

Otherwise might not compile with sanitizers enabled.

The unique connection can give a runtime exception, likely because of the
multi-inheritance, what seems to be a bug in Qt.

Since it's not needed here actually, we just remove it.

This makes it easy to compile with sanitizers. For example like this:

    ECM_ENABLE_SANITIZERS='address;leak;undefined'

The old name has been deprecated.

The base variable is declared after qobject.

There is a warning comparing the raw strings.

These properties don't seem to be used, but they should still have different
names. Otehrwise a warning by Qt moc is issued.

Silences a GCC warning.

Silences a GCC warning.

Silences a GCC warning.

We don't use these functions internally and the call to XKeycodeToKeysym
produces a deprecation warning.

Before trying to fix the warning, we may simply remove the unused functions.

This makes the code more generic. Being used this way in Wrapland too.

Instead of using the separate CI image, install Wrapland from the latest
package artifact, that Wrapland's actions provide.