launch/service: check for ConditionResult on service unit
launch/service: check for ConditionResult on service unit

When a unit doesn't satisfy its conditions, systemd will report that the
unit was started but don't actually start the service. This causes bus
activation to hang when a service can't be started due to unsatisfied
conditions.

Fix this by explicitly checking for the ConditionResult property on the
service unit object.

Original-by: msizanoen1 <bd1e2a4e4fb0936848db3b56f45462e09c846afc@qtmlabs.xyz>
(adjusted some minor coding-style issues and added comments)
Signed-off-by: David Rheinsberg <1e7ff67ac6e6692b085f67edeb10803d9022c525@gmail.com>

bus1/dbus-broker