fix: wlr-services might not have started services when they are disabled
This can happen when the compositor exits, the services aren't stopped
in time, and they crash because they can't connect to wayland display.
This will make sure they get re-enabled on start of wlr-services. This
shouldn't be dangerous, because wlr-services is started just once, and
at worst if it was failing, it would get restarted 5 times and then
disabled, leading to maximum of 5*5*(count of wlr-services) restarts,
which is quite a lot, but not infinity :) Anyway wlr-services
shouldn't be crashing when configured properly (what if service
doesn't exist...?) so this shouldn't ever happen.