AsahiLocker 2.0.1 — an M3 needs m1n1 1.9.1 to boot a live USB

⚠️ See 2.0.2 first. This release suggested the Asahi installer's stage 1 m1n1 upgrade without a warning. It worked on an M3 Air but left an M2 Max on macOS 27 unbootable. Upgrade stage 2 with dnf first.

A patch release. Nothing changes in how a volume is encrypted, in the KDF,
or in any volume an earlier release made. The one code change is a warning.

M3: m1n1 1.9.1 or later (#4)

On an M3 MacBook Air with m1n1 1.6.x, U-Boot finds no USB mass storage at
all. usb start reports no storage device whatever stick and port you try,
so the live USB never shows up in bootflow. m1n1 1.9.1 fixes it. Reported
and solved by @ljrk0.

• docs/LIVE-USB.md: a new section, M3: m1n1 1.9.1 or later. It shows
  how to read both m1n1 stage versions from /proc/device-tree/chosen/, how
  each stage is upgraded (stage 1 through the Asahi installer's option m
  from macOS, stage 2 with dnf upgrade m1n1), and the second-install route,
  which needs no USB.
• luks-deploy.sh: on an installed M3 (t8122) system, it warns when
  either m1n1 stage is below 1.9.1 or has no version recorded. It is a
  warning only; nothing is refused.
• docs/COMPATIBILITY.md: the M3 MacBook Air row points to the section.

As of this release the regular installer (alx.sh, v0.9.2) still bundles
m1n1 1.6.1. Only the development installer (alx.sh/dev) has 1.9.x.

Also since 2.0.0

• docs/LIVE-USB.md: if a boot from the stick hangs on a dev-disk-by-uuid
  job, unplug and replug the stick. Linux never enumerates a USB device that
  was attached at power-on (AsahiLinux/linux#554). Reported in #3.
• The docs now state that AsahiLocker is for Apple Silicon (aarch64) only;
  every other machine is LinuxLocker's job.
• CI runs on aarch64 only, now with actions/checkout v7 (Node 24).
• README: the audit section names the audits for what they were, and the
  project is described as free and open source.