Switch to the mise-bin package (#7244)

* Switch to the mise-bin package

mise-bin carries mise's own release artifacts from the Omarchy repo --
PGO+BOLT-optimized on x86_64, glibc-native on both arches -- instead of
Arch's mise, and tracks jdx/mise releases directly.

Existing installs need a migration because the two packages conflict, and
omarchy-pkg-add cannot make the swap: pacman answers its own conflict
question with No under --noconfirm and fails the transaction. --ask=4
answers that one question, so mise-bin replaces mise in a single
transaction -- which is also what keeps omarchy-zsh and omarchy-fish, both
of which depend on mise, satisfied through the swap by its provides.

* Guard the swap with a conditional instead of an early exit

Two-path control flow takes an if, per the style guide; the early exit only made the swap line unreachable from a distance.

install/omarchy-base.packages

@@ -78,7 +78,7 @@ lua51
 luarocks
 man-db
 mariadb-libs
-mise
+mise-bin
 moonlight-qt
 mpv
 mpv-mpris

migrations/1786952219.sh

@@ -0,0 +1,17 @@
+echo "Switch mise to the mise-bin package from the Omarchy repo"
+
+# mise-bin carries mise's own release artifacts -- PGO+BOLT-optimized on x86_64,
+# glibc-native on both arches -- and takes over from Arch's mise, which it both
+# provides and conflicts with.
+#
+# The swap has to happen in one transaction. Removing mise first breaks
+# omarchy-zsh and omarchy-fish, which depend on it; the provides is what keeps
+# them satisfied when mise-bin lands in the same transaction that drops mise.
+#
+# omarchy-pkg-add cannot do that swap: pacman answers its own conflict question
+# with No under --noconfirm and fails the whole transaction ("unresolvable
+# package conflicts detected"). --ask=4 is that one question, answered yes.
+
+if omarchy-pkg-missing mise-bin; then
+  sudo pacman -S --noconfirm --ask=4 mise-bin
+fi