SearXNG deploy: do not systemctl enable the generated units

Quadlet units are generator-managed; systemctl enable fails on them
('transient or generated'). The [Install] WantedBy=default.target in each
.container file is itself the enablement (is-enabled reports 'generated'), and
with user linger on they start at boot. Drop the enable step; daemon-reload and
start are enough.

scripts/deploy-searxng-quadlet.sh

@@ -77,11 +77,13 @@ echo '  Copying quadlet units into ~/.config/containers/systemd/ ...'
 mkdir -p ~/.config/containers/systemd
 cp ${QDIR}/*.container ${QDIR}/*.network ~/.config/containers/systemd/
 
-echo '  daemon-reload + enable the container units for boot...'
+echo '  daemon-reload (generates the units)...'
-# The .network unit is generator-managed: it cannot be enabled, and it is pulled
+# Quadlet units are generator-managed: systemctl enable fails on them ("transient
-# in automatically by the containers that set Wants=/After=searxng-network.service.
+# or generated"). The [Install] WantedBy=default.target in each .container file is
+# itself the enablement (is-enabled reports "generated"), and with user linger on
+# they start at boot. The .network unit is pulled in by the containers that set
+# Wants=/After=searxng-network.service. So: daemon-reload, then start.
 systemctl --user daemon-reload
-systemctl --user enable gluetun.service searxng-valkey.service searxng.service
 
 echo '  Starting in dependency order...'
 systemctl --user start searxng-network.service