Since GNOME 3.34, mouse accessibility is implemented by libmutter and
gnome-shell, so that it works in both Wayland and X11. The older
implementation using mousetweaks only worked for X11.

In some cases the settings changes may be emitted when the display manager
configuration has not been initialized yet (being created asynchronously
only once the session bus is ready), and in such case we should just
ignore any request involving the display configuration, given that it will
be performed again once we've it ready. Otherwise we could crash.

LP: #1887731

No need to read gsettings to fetch the actual fractional scaling state, as
mutter gives us such informations on the real state, without having us to
deal with the settings state manually (also because the state may depend
on other aspects as well).

We can also allows to remove the GDK usage in the model and work correctly
in both X11 and wayland.

Ensure the user is requested to apply changes if the requested configuration
uses UI scaling and the current widget scaling value doesn't match the
requested one.

LP: #1887707

This allows to enroll multiple fingers

LP: #1873298

  - sound: Stop non-interactive profile changes from triggering
    changed events, fix selection issues (lp: #1885673)

When fractional scaling is enabled we can just apply it promptly, as it will
preserve the current integer settings anyways, in case it's disabled,
instead we may have to reset the monitor scaling to integer values and
require user confirmation.

To do this, move the settings handling inside the current configuration and
in case the fractional scaling settings is reverted, ensure that we show
the user the "Apply" button and reset the parameters before doing so.

While the fractional scaling disable is pending, we won't show any
fractional value, to the user.

LP: #1876891
LP: #1876894

LP: #1871864

The dock uses its own monitors numbering for settings to make it also work
with the gtk configurations that it ships.

As per this, the matching with the CcDisplayPanel numbers (that reflect
mutter IDs) can be wrong when the primary monitor is not the monitor with
index 0.

To fix this, include into the monitor placement list store another column
that contains the monitor index as the dock would compute it, and use this
value to set the settings and select the relative list item.

LP: #1877108

Dash-to-dock uses absolute LEFT/RIGHT position setting values even in RTL
mode, but in such case it adapts the dock position correctly.

So, when we're in RTL mode, a right-positioned dock is actually in the
left of the screen and vice-versa.

As per this, use a binding with custom mapping, to invert such values when
using an RTL language.

LP: #1876937

LP: #1877441

debian/patches/0032-online-accounts-maybe-leak-a-reference-to-the-panel.patch: maybe leak a reference to the panel, to prevent a crash (LP: #1862553)