Pacstrap omarchy-installer via archinstall so /etc/skel is set up first

archinstall creates the user AFTER pacstrap. If omarchy-settings (which
ships /etc/skel/.config/**) isn't pacstrap'd, the user is created with
an empty skel and never gets the Omarchy default configs in their HOME.

Add omarchy-installer to the configurator's archinstall package list
(its depends pull omarchy + omarchy-settings + omarchy-limine), so all
the package files are in place before the user is created.

install_omarchy no longer needs the explicit 'pacman -S omarchy-installer'
step; it just runs 'omarchy-install' which is already at /usr/bin/.

configs/airootfs/root/.automated_script.sh

@@ -47,13 +47,13 @@ install_arch() {
 }
 
 install_omarchy() {
-  # Install the omarchy meta-packages from the offline mirror into the target.
-  # omarchy-installer's depends pull in omarchy + omarchy-settings + omarchy-limine.
-  arch-chroot /mnt pacman -S --noconfirm --needed omarchy-installer
+  # omarchy-installer (and its depends omarchy + omarchy-settings + omarchy-limine)
+  # are pacstrap'd by archinstall via the configurator's packages list, so they
+  # land BEFORE archinstall creates the user — meaning /etc/skel/.config is in
+  # place and the user's $HOME is seeded with the Omarchy defaults at creation.
 
   # Run the installer's offline path. omarchy-install execs /usr/share/omarchy/
-  # install.sh; OMARCHY_INSTALL_MODE=offline tells it to skip first-run-mode
-  # the right way for a chroot install.
+  # install.sh; OMARCHY_INSTALL_MODE=offline tells it the chroot install rules.
   chroot_run_as_user "OMARCHY_INSTALL_MODE=offline omarchy-install"
 
   configure_login_for_unencrypted_install

configs/airootfs/root/configurator

@@ -479,7 +479,8 @@ cat <<-_EOF_ >user_configuration.json
         "base-devel",
         "git",
         "omarchy-keyring",
-        "snapper"
+        "snapper",
+        "omarchy-installer"
     ],
     "profile_config": {
         "gfx_driver": null,