Mutter changes the backlight property on VT switches and monitor
reconfigurations, to tell us both whether there are any controllable
backlight, or if there is any backlight to potentially control from
somewhere else. If we control the backlight via e.g. sysfs/udev,
such a signal emission would inadvertently reset the backlight because
we'd think we went from having controllable backlight to not having it,
which isn't true if that backlight was controlled via sysfs.

Handle this by making the backend in control of the backlight explicit,
and only attempt to reset the backlight fields on mutter signal
notifications, if the mutter backlight backend is used.

Closes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/818

We were trying to update the mutter backlights before we had mutter up
and running, but this may happen after the plugin has started (I guess
especially when using non-systemd based gnome-session), so let's just
wait for the display config to be around before trying to get data from
it.

Update to upstream version '47'
with Debian dir e0b7b789e87c06d2c10b98c8c3d41228da98d204

This fixes version number so it sorts better

Otherwise previously, meson would think it's older than alpha/beta/rc

```
Dependency found: NO. Found 47 but need: '>= 47.beta'
```

Related https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/91

Fixes https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/821

Part-of: <https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/387>

So we avoid the issue in the future

Related to https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/821

Part-of: <https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/387>

Update to upstream version '47.1'
with Debian dir d172f2559db5ca28563078985839bd6876245e57

Mitigates: #1081417, #1018437, #1081439, #1081440

Gbp-Dch: Full

tagging package gnome-settings-daemon version debian/47.1-1