reboot doesn't honor disk encryption setting in earlier tinkerbell action during EKS anywhere cluster creation for bare metal

**What happened**:
I try to introduce disk encryption in EKS anywhere cluster for bare metal as follows:
I try to setup the the disk encryption for directory like /var in a tinkerbell action (right before tinkerbell action reboot).
Everything looks good in following areas:

1. /dev/mapper/ has cryption target name "sda1_crypt"
2. /etc/fstab maps "/var" to "/dev/mapper/sda1_crypt" with type "ext4"
3. /etc/crypttab maps target "sda1_crypt" to partition "/dev/sda1", which is consistent with output of "fdisk -l"

Only interesting thing is that, after command "cryptsetup luksOpen /dev/sda1 sda1_crypt" in the tinkerbell action, dummy file /etc/crypttab is not generated (if we run the command in command line, we will see /etc/crypttab shows up with a comment line).

However, tinkerbell action "reboot" doesn't ask for passphrase, and after reboot, all the cryption setting mentioned above disappears.

**What you expected to happen**:
I expected reboot will ask for encryption passphrase, and after reboot, the encryption settings will stay

**How to reproduce it (as minimally and precisely as possible)**:

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:

The report does not name a file, test, or code entry point. Start by reproducing bare-metal cluster creation with a Tinkerbell action that encrypts /var before reboot, then inspect the reboot action and its handling of /etc/crypttab and /etc/fstab. Done means the reboot preserves the encryption settings and requests the passphrase afterward.

Written by the indexing model from the issue text.