Make compatible with cryptsetup's encrypt hook

This merge request makes archiso hook compatible with the correct output of the encrypt hook, that can so be enabled and configured to handle LUKS encrypted archiso systems.

Changes

When the encrypt successfully ends, it exports a static root variable containing the path of the device mapper representing the root device (by default /dev/mapper/root).

Since the root device here is on a file on the bootmnt and not on a disk directly, I've changed the cryptsetup encrypt hook to support an intermediate mount for bootmnt on /run/cryptdev.

Compatibility is obtained by bind mounting /run/cryptdev to bootmnt and replacing the loopmount with root if it exists.

Value of archisodevice has been changed from /dev/disk/by-label/$archisolabel to dev/disk/by-uuid/$archisouuid to avoid boot problems when multiple archisolabel'd devices are inserted.

Depends on nested cryptkey support cryptsetup merge request (where should it be submitted for review?).

Solves #14 and #15 (moved).

See specular MR on archlinux/archiso!217 (closed).

hooks/archiso

@@ -54,6 +54,18 @@ _mnt_overlayfs() {
         airootfs "${newroot}${mnt}"
 }
 
+# args: /path/to/image_file
+_open_luks() {
+    local img="${1}"
+    local img_fullname="${img##*/}"
+    local map="${img_fullname}.map"
+    is_luks=$(blkid -s TYPE -o value "${img}")
+    if [ "${is_luks}" = "crypto_LUKS" ]; then
+        cryptsetup luksOpen "${img}" "${map}"
+        dev="/dev/mapper/${map}"
+    fi
+}
+
 # args: /path/to/image_file, mountpoint
 _mnt_fs() {
     local img="${1}"
@@ -105,6 +117,8 @@ _mnt_dev() {
         launch_interactive_shell
     done
 
+    _open_luks "${dev}"
+
     if mount --mkdir -o "${opts}" "${flg}" "${dev}" "${mnt}"; then
         msg ":: Device '${dev}' mounted successfully."
     else