init: always run cryptsetup hook with secure boot

[jakogut]

Init hooks specify an *_enabled function that determines whether or not the hook is skipped during boot. Hooks are run by the "init" script, shipped as part of the initramfs-framework poky recipe.

Several conditions were checked in the cryptsetup-efi-tpm enablement function, some of which could cause the hook to be improperly skipped.

Force the hook to run when in secure boot user mode, as we want any failure in the hook's run function to be detected and abort the boot.

Change-type: patch

---

Contributor checklist

• [ ] Changes have been tested
  • [ ] Covered in automated test suite
  • [ ] Manual test case recorded
• [ ] Change-type present on at least one commit
• [ ] Signed-off-by is present
• [ ] The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[github-actions[bot]]

Website deployed to CF Pages, 👀 preview link https://1b897eb9.balena-os.pages.dev