The function obex_agent_down (and consequently obex_agent_dispose) can be called
while we are still waiting for the bus to be acquired. Add if-guards to ensure
that we do try to reference invalid memory and/or handlers.

Closes: gnome-control-center#425

The autopair plugin has lived in bluez since 2013, so it's about time we
made use of it, and removed duplicate quirks.

This tablet cannot pair, and expects to just to connected to and set to
"Trusted".

Full manual at:
https://www.wacom.com/-/media/wacomdotcom/files/store-manuals/legacy-models/graphire-bluetooth-manual.pdf

Back in the heady Bluetooth 2.0 days, the majority of pointer devices
could work without pairing, and some did not even support pairing.

But pointer devices really want pairing for all the subsequent versions
(from "Secure Simple Pairing" in Bluetooth 2.1, 2007), so always try to
pair pointer devices.

The device path in the data struct was never freed even though we owned
it. Small leak that only happened when pairing, so low impact.

bluetooth_client_setup_device_finish() stole the device path from the
result object but didn't mention it. Clarify the ownership of the "path"
return value.

The guard was guarding against a local variable ("device") being
NULL, instead guarding against one of the arguments ("device_path")
being NULL. Depending on the compiler and runtime, this would probably
fail most of the time, leading to problems using non-pairing devices
after the initial setup.

bluetooth_client_set_trusted: assertion 'device != NULL' failed

Fixes: 27e88fc0

As with discoverability, we need to disable discovery when the settings
widget is destroyed. This fixes an issue where we keep discovering when
switching away from the bluetooth panel in g-c-c. This is mainly an
issue as it may impact the performance of established bluetooth
connections.

Discoverability is automatically disabled again on widget finalization.
Remove the old fixme as the issue has been solved since.

The mouse's manual doesn't give any details on how to pair
it, but it claims to be "Mac only", so the behaviour was likely
the same one as Apple's own mice, with a "0000" pincode.
This was tested successfully.

Added it to POTFILES.skip but didn't remove it from POTFILES.in.

The 3.29 release cycle has already come and gone, we should be releasing
for the 3.31 cycle.

Fixes gnome-control-center#364

This fixes the name collision in GNOME Settings.

This is a fork of HdyColumn introduced to fix a name collision in GNOME
Settings as is has both gnome-bluetooth's version of HdyColumn and its
own in parallel.

The widget couldn't be named BluetoothColumn as the name was already
taken.

settings-widget: Use a Hdycolumn

See merge request !4

This allows to better test the size adaptation of the widget.

This stops the labels flickering when they are ellipsized and the
window's size changes.

This adapts the indentation of the children of HdyColumn, which were
deliberately left intact in the previous commit to make it more
readable.

Put the widget's content into a HdyColumn to better manage the available
width.

This deliberately doesn't adapt the indentation of the contained widget
to help this commit to be more readable and easier to review, it will be
adapted in the next commit.

This will be needed by the next commit to access HdyColumn.

This also lets the CI recursively update the submodules so it can pass.

(cherry picked from commit c080ec21)

Different meson improvements

See merge request !6