Now that we work decently well on thin screens, let's mark our
support for mobile form factors using the non-standard
X-Purism-FormFactor for now.

In theory, this same information is in the metainfo file, but
phosh at least still only looks in the desktop file for this.
So let's help it out.

(cherry picked from commit 965ac138e49ac26342d3997c57f62c12bb3ea578)

Not much of a difference yet, except that the surface of the dialog
is draggable.

Only used when building against libadwaita 1.2 (which at the time of
writing is not yet released). Building against older versions will
continue to use GtkMessageDialog.

There's enough coming in libadwaita 1.2 (notably AdwEntryRow) that
I'd like to use that we might as well bite the bullet and require
it.

Since this is a major enough packaging change, let's also bump
our major version number.

This scales better on small screen widths and is hopefully a more
standard look.

Also add configure_entry_row() to do some common tweaks for entry
rows.

Now that libadwaita exposes them, we don't need the indirect
method used before.

And also turn off deprecation warnings if tests are being run
inside devenv, to avoid false negatives.

It only really searches the first page anyway. And competes for
horizontal space with the view switcher.

Require libadwaita 1.2, bump version to 44.0, and use new widgets

See merge request World/deja-dup!75

- Switch from GtkBox widget parents to AdwBin where appropriate,
  to keep the class boundaries cleaner
- Switch from setting the "child" property to using <child> where
  possible, as it feels more obvious & consistent to me
- Hide TimeCombo's inner workings a bit from external users by not
  setting the outer "visible" property ourselves
- Remove a no-longer-used GtkStack wrapper from MainHeaderBar,
  since we dropped the separate selection-mode header bar

This enables support for linking with packagekit and installing
runtime dependencies on the fly. Previously, this was detected
at build time based on whether packagekit libraries were installed.

This change just makes it more explicit and also disabled by
default. (I chose 'disabled' rather than 'auto' as the default,
because distros often set -Dauto_features=enabled and this
feature is not encouraged as a UX flow.)

Also, this bumps the required version up to 1.2, in order to drop
the annoying I_KNOW_... build flag definition.

Add a more distro-packager friendly doc, to help navigate the growing
list of meson options.

And tweak related documentation to account for these changes.

build: add PACKAGING.md and document meson options better

See merge request World/deja-dup!76

(cherry picked from commit e2efb7110913dc022648b884cddba0403be9a4b4)

Support for pydrive (vs pydrive2) is going to be dropped in
duplicity 1.0.0, so let's not bother mentioning it in the
packaging guide.

If both password entries match, highlight them both. Might help
the user understand why we are highlighting them better.

This enables compression in restic repositories. I'm not bothering
to add support for upgrading version 1 repos right now, since we
are so early in our restic support.

- Add initial.test test script
- Bump minimum restic to 0.14.0

Update dependencies, use restic repo-version 2

See merge request World/deja-dup!77

Settings.delay can appear to get stuck in delay-apply mode, possibly
in cases where there are not actually changes to apply when apply()
is called.

It's not super important that we group the changes, so let's just
avoid ever delaying a settings for a moment.

Fixes: https://gitlab.gnome.org/World/deja-dup/-/issues/330

DejaDup.configure_entry_row would set a couple properties
that were awkward before libadwaita 1.2 came out -- now they
are builtins. So just use the properties directly.

Now that xdg-desktop-portal exposes a "GameMode is active" property,
check that as well as the actual game mode desktop service.

Once the new portal is deployed everywhere, our flatpak releases could
eventually stop poking a hole in the container for the game mode
service.

Remove a workaround for a visual bug that doesn't seem to be
present anymore. And removing it fixes the bottom switcher bar
to show up on startup again, if the width is small.