Collect all the parent of a given device and pass that to the device
dialog, so we can show and potentially authorize/enroll all the
parent devices too.

Add an expander that contains a list of all the parent devices of
the dialog's target device. If any of the devices is not yet
authorized, show a warning symbol next to it.
Additionally the enroll/authorize function calls are replaced
by a single bolt_client_connect_all call, so parents that need
authorization can be authorized/enrolled too.

The CcBoltDeviceEntry can now optionally show a warning indicator
if the device is in the pending state.
Since we *don't* want to show this in the main list, remove calls
to gtk_widget_show_all and replace them with gtk_widget_show.

Adds a utility function that deterministically generates an object
path from a path base and an object id.
The corresponding bolt commit is:
  a396eb986611ed73fc0ccca2127f29ab1e3aac62

Import five commits that add methods to enroll and authorize multiple
devices at once; meant for authorizing a target device and all the
parents that need to be authorized.
Commits in bolt are:
  1ae5c8611fc21c21c8c63ba6933b63eb4c20ab87
  d993ca2f871e7e412b4e1f885b24e4f6622dfc55
  2689e5f77496ac7698744e582feb9afa3e55e0ac
  87762ce14650263ef35f97da5a3a5d122ac0b7d7
  5aa5548d6c7fa1fa26733ecd073097bc1b9d31fb
  00b3d8a35835b8c856e5de026a0c8316b2ceba90

It is almost surreal to believe that there's a leak in
libasan, but this is blocking CI and it's not something
we can work on right now.

Suppress this leak.

We already have a release in Rawhide, no need to keep
the custom build around anymore.

[skip ci]

[skip ci]

It's a dependency of the new Sound panel.

Christian Kellner authored Jan 23, 2019 and Benjamin Berg committed Jan 30, 2019

Listen for security level changes, which in theory should not really
happen at all with the exception that on hardware where force power
is not support and boltd has not yet seen the thunderbolt controller
because it was powered down. Then we should get an initial change
from 'unknown' to the real level. Handle it in the same way that
as if boltd was restarted, i.e. the dbus name owner changed

Christian Kellner authored Jan 23, 2019 and Benjamin Berg committed Jan 30, 2019

If bolt cannot determine the security level, which in theory should
never happen[1] the standard no-thunderbolt message seems not
entirely appropriate. Instead show a different message that is more
tailored to this unusual case.

[1] The following (unlikely) reasons would invoke such a scenario:
   - new security level not supported by boltd
   - old hardware with not force-power support and the thunderbolt
     controller has not yet been powered up

Christian Kellner authored Jan 23, 2019 and Benjamin Berg committed Jan 30, 2019

Should not happen very often in the real world, but ever time the
name owner changed (i.e. boltd was restarted) the name_owner
variable was leaked.

Use the dialog cancellable instead of leaking one each time the PPD is set.

Otherwise this could crash if the dialog is destroyed before the PPD is set.

The cancellable is only used to cancel when the dialog is destroyed, so you can
share it for all calls.

Use g_clear_* functions to simplify code and ensure values are set to NULL after freeing.

This allows the panel to reach narrower widths.

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

This will allow the panel to reach smaller sizes.

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 allows the panel to better adapt to the available width.

This widget now uses libhandy for the rows.

libhandy now has HdyValueObject, this simply copies the class over as it
will only become available in libhandy 0.8.

It will be used from multiple files in the future.