[loginmanager — crates/loginmanager-daemon/src/config.rs, crates/loginmanager-daemon/src/server.rs, loginmanager.toml] Arm autologin from any of several condition paths, and dispatch the session by which marker exists
Autologin gated on a single `condition_path`, which only fit the install medium: the marker was `install-pending` and the session was always the installer kiosk. A device flashed straight to its final disk (an eMMC, a PC) has nothing to install, so its first boot goes through the eydos-installer Configure flow instead, marked by `configure-pending` and run on the full desktop with the wizard on top. That path needs autologin too, and a different session, and the single-path config could express neither — the greeter came up asking for a password.
`AutologinEntry.condition_path` becomes `condition_paths: Vec<PathBuf>`, and the daemon arms autologin when the list is empty or any of the paths exists. The TOML gains `condition_paths` (a list); the singular `condition_path` is still accepted and folded into the list, so existing configs keep working. The shipped `loginmanager.toml` lists both `install-pending` and `configure-pending`, and points `command` at `/usr/bin/eydos-firstboot-session`, a dispatcher that execs the kiosk installer session while `install-pending` exists and the full desktop session otherwise — so the live medium autologs into the wizard kiosk and a directly-flashed first boot autologs into the desktop-plus-configure flow, while a finished setup, which retires both markers, never logs in automatically.
# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# En la rama master
# Tu rama está actualizada con 'origin/master'.
#
# Cambios a ser confirmados:
#	modificados:     crates/loginmanager-daemon/src/config.rs
#	modificados:     crates/loginmanager-daemon/src/server.rs
#	modificados:     loginmanager.toml
#
