v1.2.0: Manjaro SafeAUR Updater 1.2.0

Manjaro SafeAUR Updater 1.2.0

aurinstall now builds in a Manjaro chroot by default.

Suggested by linux-aarhus of the Manjaro team during review of the
announcement thread: manjaro-chrootbuild builds inside a chroot synced to a
chosen Manjaro branch, so an AUR package is compiled against the libraries
you actually run rather than whatever the AUR assumed. That is a build-time
fix for the same soname mismatch aur-rebuild-check could only report after
the fact. Build dependencies stay in the chroot.

It is gated, not unconditional. A survey of one real system: 42 of 49
installed AUR packages were chroot-eligible, 7 needed AUR dependencies
chrootbuild cannot resolve, 1 was a -bin. The gate falls back to yay and
always names which check tripped; --chroot turns the fallback into an
error, --no-chroot forces yay, AURINSTALL_MODE sets the default.

Also in this release:

• --ignore cannot manufacture a partial upgrade -- now proved by a test
  against real pacman transactions rather than argued. pacman resolves
  the whole transaction and refuses one that would strand a dependency,
  changing nothing; pacman -Dk stays clean. A real safeup hold inherits
  that. README carries the transcript.
• Scope narrowed to Manjaro only. The problem is created by Manjaro
  Stable trailing Arch, and the build path is now Manjaro own tooling.
• manjaro-chrootbuild is a required dependency, installed by deploy.sh.
• The Manjarno citation was dropped from the README.

62 assertions across two suites, shellcheck -S warning clean, no runtime
dependency beyond pacman, coreutils, yay and manjaro-chrootbuild.

v1.1.0

fix lint test error