flake: update nvf dev input

[trueNAHO]

Update the nvf dev input to pull commit [1] ("flake: follow flake-parts
and flake-utils inputs"), reducing our number of unique dependencies.

[1]: https://github.com/NotAShelf/nvf/commit/607675ac6e1c99318c65b4ffc4a87d935d787072

For reference, if NotAShelf/nvf#1001 gets merged, it further decreases our number of unique dependencies. Since it only affects nvf's internal inputs, this requires no additional action on our end other than updating nvf.

-- #1579 (review)

With NotAShelf/nvf#1001 merged, this PR pulls only the desired changes: NotAShelf/nvf@a82b228...8ea010d.

Things done

• Tested locally
• Tested in testbed
• Commit message follows commit convention
• Fits style guide
• Respects license of any existing code used

Notify maintainers

[0xda157]

thanks for doing that

[stylix-automation]

Backport failed for release-25.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.05
git worktree add -d .worktree/backport-1673-to-release-25.05 origin/release-25.05
cd .worktree/backport-1673-to-release-25.05
git switch --create backport-1673-to-release-25.05
git cherry-pick -x 0da583a359fd911d5cbfd2c789424b888b777a4b

[stylix-automation]

Successfully created backport PR for release-25.05:

• [release-25.05] flake: update nvf dev input #1684

[trueNAHO]

@awwpotato, remember to include the original commit message (or a reworded version) in the final squash commit message when appropriate. For example, this seems to have been missed in this PR and #1659.

[0xda157]

@awwpotato, remember to include the original commit message (or a reworded version) in the final squash commit message when appropriate. For example, this seems to have been missed in this PR and #1659.

yeah sorry about that I'll make sure to look over the pr description and comments before merging in the future.

[trueNAHO]

[awwpotato], remember to include the original commit message (or a reworded version) in the final squash commit message when appropriate. For example, this seems to have been missed in this PR and #1659.

yeah sorry about that I'll make sure to look over the pr description and comments before merging in the future.

From my experience, GitHub never populates the commit body with the original commit message. Very occasionally, it at best copy-pastes the entire PR description, which is obviously very bad.