v0.5.14: remove plymouth package entirely

v0.5.13 added omit_dracutmodules+=plymouth + dracut --force regen in
chroot %post. Boot test still showed plymouth-start.service running.
Theory: the chroot dracut --force --kver loop didn't fire (kver glob
may have been empty in chroot), or anaconda regenerated initramfs
AFTER our %post and ignored our config drop-in.

Simpler fix: don't ship plymouth at all. Add `-plymouth
-plymouth-plugin-label -plymouth-system-theme` to kickstart %packages.
With no plymouth package on disk, dracut can't bundle it into
initramfs regardless of dracut.conf state.

The /etc/dracut.conf.d snippet + /dev/null masks from v0.5.12-13 stay
as belt-and-braces — harmless once plymouth is absent.

overlay/usr/local/bin/veilor-installer

@@ -407,7 +407,9 @@ policycoreutils-python-utils
 tuned
 chrony
 firewalld
-plymouth
+# plymouth: removed in v0.5.13. Splash unreliable in QEMU; LUKS prompt
+# falls back to systemd-tty-ask-password-agent on tty1 (text). Cleaner
+# boot, smaller initramfs, fewer moving parts.
 
 # admin essentials
 git
@@ -435,6 +437,9 @@ zram-generator
 -kde-connect
 -open-vm-tools-desktop
 -mlocate
+-plymouth
+-plymouth-plugin-label
+-plymouth-system-theme
 
 %end