manager: persist the host device

When the thunderbolt controller is in non-native enumeration mode,
it is only powered by the firmware when something is plugged into
the thunderbolt port. In those cases the domain and device nodes
are missing in sysfs and we have no information about the host
device, including the (new) generation attribute. Always persisting
the host solves that issue and does no harm in native enumeration
mode either.

boltd/bolt-manager.c

@@ -1280,12 +1280,16 @@ manager_maybe_import (BoltManager *mgr,
    * could be, but since it is security critical, it is
    * better to be clear than concise */
 
-  if (bolt_device_get_device_type (dev) == BOLT_DEVICE_HOST)
-    return;
-
   g_return_if_fail (!bolt_device_get_stored (dev));
   g_return_if_fail (bolt_device_is_authorized (dev));
 
+  if (bolt_device_get_device_type (dev) == BOLT_DEVICE_HOST)
+    {
+      /* Store the host device, which is always authorized */
+      manager_do_import_device (mgr, dev, BOLT_POLICY_MANUAL);
+      return;
+    }
+
   level = bolt_device_get_security (dev);
   iommu = bolt_device_has_iommu (dev);
   boot = bolt_device_check_authflag (dev, BOLT_AUTH_BOOT);