Also allow skipping the questions for non-interactive scripts.

Recoldplug is really not required for the USB based plugins, and we should
restrict this action to plugins that have inter-dependencies on each other.

Deduplicate based on the ID, without assuming the devices will be the same
in-memory object. Also, only emit the changed signal if the device is waiting
for a replug.

Fixes https://github.com/hughsie/fwupd/issues/364

When searching for a device by id, also include the old device in the search.

The convention we're using is that find() returns the FuDeviceItem and get()
returns the FuDevice, so be consistent.

No code flow changes.

These are devices that UEFI capsule support is turned off in BIOS
setup.  Unlocking them can turn UEFI capsule support

In the case of failing to even set up UpdateCapsule, the uefi plugin would
dutifully return SUCCESS as it was referring to the 2nd-to-last update that
actually worked.

This allows us to use a FwupdDevice or just use a string for testing.

This ensures we can restart the fwupd service without marking updates that need
a reboot as failed.

This reverts commit 47ff62b9.

This lets master build on Ubuntu 17.10.
Ubuntu 17.10 doesn't have the newer appstream-glib, so reverting
this commit means Ubuntu 17.10 can't use the HWID's stuff from
b8f8db20
without a manual backport.

Ubuntu 18.04 and later already have the newer appstream-glib
though, so they will get the HWIDs functionality

The SUPPORTED flag is used when a device appears in the AppStream metadata of
any enabled remote, so when we rescan the modified store also ensure the flag
state is still correct.

Fixes https://github.com/hughsie/fwupd/issues/363

If a user disables the reporting URI, we don't want to re-enable it
accidentally when upgrading fwupd.

The work for this landed in what will turn into efivar 33.

Later down the road when efivar 33 is in most the major distros
this can be removed and a requirement set for efivar 33.

This is supposed to be a gentle nag, rather than being obnoxious. To disable
this, simply remove the ReportURI key from the relevant remote.

This shares your history with a reporting server, typically the LVFS.

NOTE: no data is sent without the user opting-in, and the data sent is shown to
the user before upload.

Save the dependency versions, architecture and the kernel versions in the
history database as metadata as it may be different to the time of upload.

This will be used to store things like the kernel version in the future, and
also means we can stop abusing the vendor property for the fwupd version.

This allows us to use the other keys for future use.

This allows us to set specific flags on the device stored in the database.

This flag is present in the history database when a report has been uploaded.

This has to be done at each engine startup, as this will happen on the *next*
OS boot.

This needs to be run as the root user to work.

Rename FuPending to FuHistory to better represent what the object is now doing.
Also, while we're here, switch to using SQLite prepared statements to avoid a
possible invalid read on i386 hardware.

This is for future use.

This allows us to identify a specific machine using the machine-id.