[main] Update flake.lock & generated files

[github-actions]

Root lockfile

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/ed30f8aba41605e3ab46421e3dcb4510ec560ff8?narHash=sha256-5oLdRa3vWSRbuqPIFFmQBGGUqaYZBxX%2BGGtN9f/n4lU%3D' (2025-05-04)
  → 'github:NixOS/nixpkgs/b3582c75c7f21ce0b429898980eddbbf05c68e55?narHash=sha256-FshoQvr6Aor5SnORVvh/ZdJ1Sa2U4ZrIMwKBX5k2wu0%3D' (2025-05-07)

Dev lockfile

Flake lock file updates:

• Updated input 'dev-nixpkgs':
    'github:NixOS/nixpkgs/ed30f8aba41605e3ab46421e3dcb4510ec560ff8?narHash=sha256-5oLdRa3vWSRbuqPIFFmQBGGUqaYZBxX%2BGGtN9f/n4lU%3D' (2025-05-04)
  → 'github:NixOS/nixpkgs/b3582c75c7f21ce0b429898980eddbbf05c68e55?narHash=sha256-FshoQvr6Aor5SnORVvh/ZdJ1Sa2U4ZrIMwKBX5k2wu0%3D' (2025-05-07)
• Updated input 'git-hooks':
    'github:cachix/git-hooks.nix/dcf5072734cb576d2b0c59b2ac44f5050b5eac82?narHash=sha256-DwOTp7nvfi8mRfuL1escHDXabVXFGT1VlPD1JHrtrco%3D' (2025-03-22)
  → 'github:cachix/git-hooks.nix/fa466640195d38ec97cf0493d6d6882bc4d14969?narHash=sha256-Wb2xeSyOsCoTCTj7LOoD6cdKLEROyFAArnYoS%2BnoCWo%3D' (2025-05-06)
• Updated input 'home-manager':
    'github:nix-community/home-manager/8a318641ac13d3bc0a53651feaee9560f9b2d89a?narHash=sha256-i6BoiQP0PasExESQHszC0reQHfO6D4aI2GzOwZMOI20%3D' (2025-05-05)
  → 'github:nix-community/home-manager/708074ae6db9e0468e4f48477f856e8c2d059795?narHash=sha256-Mp5Bbvb%2BYlFEZ76C/0wFS6C1lRfH3D60u465wFNlnS0%3D' (2025-05-07)

Generated files

• Updated lspconfig-servers.json

---

This PR was most recently updated by workflow run 14892127504.

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.

[mergify]

This pull request, with head sha 6597afe2097ba07fdf515a541a2a02a7e06768cd, 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 6597afe2097ba07fdf515a541a2a02a7e06768cd 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.