Remove Before=libvirt-guests.service from other services

libvirt-guests has After= dependency for all the sockets and that is enough.
With the extra Before= in the service file systemd postpones the start of the
socket activated service (when libvirt-guests is trying to connect to the
socket) until after libvirt-guests is stopped effectively making `systemctl stop
libvirt-guests` deadlock.  The reason for that is that all stop jobs are
scheduled before any start job.  Removing the redundant Before= specification
fixes this behaviour.

Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>

src/ch/virtchd.service.in

@@ -5,7 +5,6 @@ Requires=virtchd.socket
 Requires=virtchd-ro.socket
 Requires=virtchd-admin.socket
 Wants=systemd-machined.service
-Before=libvirt-guests.service
 After=network.target
 After=dbus.service
 After=apparmor.service

src/lxc/virtlxcd.service.in

@@ -5,7 +5,6 @@ Requires=virtlxcd.socket
 Requires=virtlxcd-ro.socket
 Requires=virtlxcd-admin.socket
 Wants=systemd-machined.service
-Before=libvirt-guests.service
 After=network.target
 After=dbus.service
 After=apparmor.service

src/qemu/virtqemud.service.in

@@ -7,7 +7,6 @@ Requires=virtqemud.socket
 Requires=virtqemud-ro.socket
 Requires=virtqemud-admin.socket
 Wants=systemd-machined.service
-Before=libvirt-guests.service
 After=network.target
 After=dbus.service
 After=apparmor.service

src/remote/libvirtd.service.in

@@ -9,7 +9,6 @@ Wants=libvirtd.socket
 Wants=libvirtd-ro.socket
 Wants=libvirtd-admin.socket
 Wants=systemd-machined.service
-Before=libvirt-guests.service
 After=network.target
 After=firewalld.service
 After=iptables.service