Bump kcrypt and adapt hooks

[Itxaka]

Now we can pass the logger directly so we see the logs as usual Also set systemd debug mode before running the commands so we can see the debug output in case of failrue

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 8 lines in your changes missing coverage. Please review.

Project coverage is 52.20%. Comparing base (569c131) to head (3489e0a).
Report is 5 commits behind head on main.

Files	Patch %	Lines
internal/agent/hooks/kcrypt_uki.go	0.00%	7 Missing ⚠️
internal/agent/hooks/kcrypt.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #385      +/-   ##
==========================================
- Coverage   55.94%   52.20%   -3.75%     
==========================================
  Files          48       52       +4     
  Lines        4549     4902     +353     
==========================================
+ Hits         2545     2559      +14     
- Misses       1724     2060     +336     
- Partials      280      283       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jimmykarily]

these need go mod tidy to go away?

[Itxaka]

I have given up trying to understand go mod whatever. there is no logic to it

[Itxaka]

To test the if luks1 can be unlocked with newer kcrypt version:

• installed with https://github.com/kairos-io/kairos/releases/download/v3.1.0-alpha1/kairos-ubuntu-24.04-core-amd64-generic-v3.1.0-alpha1.iso which has the previous kcrypt versions which defaults to luks1
• installed with offline encryption
• rebooted to active and confirmed that disk is encrypted and unlocked correctly
• confirmed the luks header
  
• Confirmed that the immucore version (https://github.com/kairos-io/immucore/tree/v0.2.0) that unlocks the device has the new kcrypt(https://github.com/kairos-io/kcrypt/tree/v0.11.2) with the new methods

So basically the luks version does not affect the unlocking.

To test the new luks2 version by default:

• Built a new image with kairos-agent pointing to this branch

earthly +iso \
            --FLAVOR=ubuntu \
            --FLAVOR_RELEASE=24.04 \
            --FAMILY=ubuntu \
            --MODEL=generic \
            --VARIANT=core \
            --BASE_IMAGE=ubuntu:24.04 --KAIROS_AGENT_DEV_BRANCH=bump_kcrypt2

• Installed the iso with offline encryption
• rebooted to active and confirmed that disk is encrypted and unlocked correctly
• confirmed the luks header
  
• confirmed that immucore+agent had the proper versions of kcrypt

So basically it should not affect anything to change the default to luks2