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.

fix: waybar should require wayland-display

chore: move modules to modules subfolder

fix: wayland display service, add x wayland display service

fix: wayland-display services

Except emacs, the services did not actually
need wayland-display, only dbus. For emacs,
wayland-display is required for stuff like xdg-open
to work.

feat: add packages and services in home

* This adds a dependency on `rde`, it is used for serializing ini

* Themes package that can make a few themes of various variants
* Dconf that can load dconf on home activation
* Gtk that can set gtk theme, icon theme and pointer theme
* Kanshi, swayidle services that provide shepherd services
* A few Wayland services
* Xdg desktop portal adding a config, and the packages to profile