libnm: Ignore NoReply errors when NM has vanished from the bus

This fixes the /libnm/client-nm-running test failure when a race condition is hit:

test-nm-client:10350): libnm-WARNING **: updated_properties:
	error reading NMRemoteSettings properties:
	GDBus.Error:org.freedesktop.DBus.Error.NoReply:
	Message did not receive a reply (timeout by message bus)

What actually happens is that nm_running_changed_cb() calls GetAll() for a
NMRemoteSettings object when NM appears on the bus. If it disappears shortly
afterwards, another nm_running_changed_cb() is called which suppresses further
object updates, but the original GetAll() might not have finished yet and DBus
will generate a NoReply() response for it. We ought to ignore it.
contrib/rpm: Run make check
contrib/rpm: Use bconds
Merge remote-tracking branches 'lr/lr-unmanaged-slaves', 'lr/lr-ipv6-tokens', 'lr/lr-ap', 'lr/lr-rdisc-mtu', 'lr/lr-rpm', 'lr/lr-lxc', 'lr/lr-hostname', 'lr/lr-bond-activation' and 'lr/lr-ck-error' into integration