Drop install/first-run/gdk-scale.sh

The lua-based monitors config (~/.config/hypr/monitors.lua) ships from
skel with sensible defaults (omarchy_gdk_scale = 2, omarchy_monitor_scale
= "auto"). Hyprland handles the dynamic monitor scale at runtime via
"auto"; 'omarchy hyprland monitor scaling <N>' already updates both
omarchy_monitor_scale and omarchy_gdk_scale in monitors.lua when the
user wants to adjust.

The first-run 'detect what hyprland picked and write it back' dance
was leftover from the .conf-based config; it's redundant on the lua
flow and was the script that aborted omarchy-first-run under set -e
when it sed'd a missing monitors.conf.

bin/omarchy-first-run

@@ -21,7 +21,6 @@ if [[ -f $FIRST_RUN_MODE ]]; then
   bash "$OMARCHY_PATH/install/first-run/firewall.sh"
   bash "$OMARCHY_PATH/install/first-run/dns-resolver.sh"
   bash "$OMARCHY_PATH/install/first-run/gnome-theme.sh"
-  bash "$OMARCHY_PATH/install/first-run/gdk-scale.sh"
   bash "$OMARCHY_PATH/install/first-run/gtk-primary-paste.sh"
   omarchy-hook-install post-update "$OMARCHY_PATH/install/first-run/install-voxtype.hook"
   sudo /bin/rm -f /etc/sudoers.d/first-run

install/first-run/gdk-scale.sh

@@ -1,8 +0,0 @@
-# Persist the detected monitor scale (and matching GDK_SCALE) into
-# ~/.config/hypr/monitors.lua. omarchy-hyprland-monitor-scaling with no args
-# returns the closest preset to whatever Hyprland chose at startup; passing
-# that value back in updates both `omarchy_monitor_scale` and
-# `omarchy_gdk_scale` in the lua config so the choice survives a reboot.
-scale=$(omarchy-hyprland-monitor-scaling 2>/dev/null || true)
-[[ -n $scale ]] || exit 0
-omarchy-hyprland-monitor-scaling "$scale" >/dev/null 2>&1 || true