[main] Update flake.lock & generated files

[github-actions]

Dev lockfile

Flake lock file updates:

• Updated input 'home-manager':
    'github:nix-community/home-manager/708074ae6db9e0468e4f48477f856e8c2d059795?narHash=sha256-Mp5Bbvb%2BYlFEZ76C/0wFS6C1lRfH3D60u465wFNlnS0%3D' (2025-05-07)
  → 'github:nix-community/home-manager/50894120e8ac792a5d3046d23e4e4c4ef32cf09c?narHash=sha256-mSqWQsJYMJBI3%2BX3opqaUqeNsGQxVdaNL5iUF7a6p50%3D' (2025-05-08)

---

This PR was most recently updated by workflow run 14906216553.

You can re-run the update by going to the workflow's page or by using the gh command:

gh workflow run update.yml

If needed, you can also specify workflow inputs on the command line, using the -F --field, -f --raw-field, or --json flags.
See gh workflow run --help.

[GaetanLepage]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 36d63a7

[mergify]

This pull request, with head sha 36d63a7c3e0b28d0a2a798826a3b990867079b21, has been successfully merged with fast-forward by Mergify.

This pull request will be automatically closed by GitHub.

As soon as GitHub detects that the sha 36d63a7c3e0b28d0a2a798826a3b990867079b21 is part of the main branch, it will mark this pull request as merged.

It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch update/main, this means GitHub will fail to detect the merge.