Build settings for #13362's HOOKS baseline without a detector copy

omacom/omarchy#13362 (d0b94d98c) dropped the omarchy-hw-platform copy
omarchy-settings shipped beside its platform guard. Its 00-omarchy-hooks.conf
now asks the runtime's own detector on PATH, and keeps the busybox line where
there is none. The aarch64 settings recipes still refused any source whose
baseline names omarchy-hw-platform without that copy, so every aarch64 build
of quattro would fail once #13362 merges.

Both recipes drop that check. The copy is still installed when a source ships
the guard, as before. The test fixture follows #13362's current baseline, and
the split-layout test checks the package builds from it and ships no copy.

tests/fixtures/settings-boot/omarchy-13362/00-omarchy-hooks.conf

@@ -3,15 +3,12 @@
 # after it add their hooks to it instead of being overwritten by it.
 #
 # Apple Silicon boots a systemd initramfs, and its platform package adds the
-# firmware and encryption hooks. Every other machine keeps the busybox line. The
-# runtime's detector answers, or else the copy omarchy-settings ships for its
-# platform guard, so a settings package newer than the runtime still places a
-# Mac. Without either, the busybox line stays. A detector that cannot place the
+# firmware and encryption hooks. Every other machine keeps the busybox line, as
+# does one without the runtime's detector. A detector that cannot place the
 # machine stops the build rather than let it produce an image for the wrong
 # platform.
 _omarchy_platform=""
-_omarchy_detector=$(command -v omarchy-hw-platform) || _omarchy_detector=/usr/share/libalpm/scripts/omarchy-hw-platform
-if [[ -x $_omarchy_detector ]]; then
+if _omarchy_detector=$(command -v omarchy-hw-platform); then
   _omarchy_platform=$("$_omarchy_detector") || return 1
 fi