$ fwupdmgr --version
    client version:	0.9.6
    daemon version:	0.9.6

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

Test if g_strrstr returns NULL, as this means the string was
modified and other requests predicated on this will fail miserably.

Also make it clearer what the logic is checking.

Backported from 0.9.x with minor changes

Crashes will happen when UEFI capsule is turned off due to fwupdate
trying to do a SMI request that invalidates the buffer used by fwupd.

This is due to both fwupdate and fwupd using libsmbios in the same process.
Fixes: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1726367

Cherry picked from 0.9.x with some minor changes.

Thundebolt controller usually takes some time to wakeup and without
this the update will most likely fail.

Some Lenovo systems were inadvertently matching.

See https://github.com/hughsie/fwupd/issues/110

If this is not done the origin from the last file that was read (which might be
from Fedora, for instance) will be used. This isn't hugely important but can
give misleading and confusing unique-id's in gnome-software.

The meson build system does not let you choose the output name of the resource.

This was added for cosmetic reasons, and including the version makes the
generated html documentation change every release even if there were no API
changes.

We've been really bad at keeping these up to date, so just drop them.

These can be nuked at any time by users, so don't rely on the package manager
or installer to create these for us.

Packagers should still enable it so that tracking lost memory
in plugins is possible, but on some distros some archs don't
have valgrind available which would otherwise prevent fwupd
from running.

This is as problem currently for Debian unstable where some
archs valgrind fails to compile.