dotnet: migrate nuget lockfiles to JSON

[GGG-KILLER]

This changes the buildDotnetModule lockfiles to be JSON instead of Nix.

Changes were made in a backwards-compatible fashion, however a warning was added to guide users to migrate to the new format.

Existing in-tree packages were migrated to the new format using a helper script and manual changes for places that didn't have the file directly specified.

cc: @NixOS/dotnet @MattSturgeon @UlyssesZh @TomaSajt @SuperSandro2000 @Atemu

Closes #362182, closes #325053.
Fixes #358025.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[MattSturgeon]

Initial minor questions/suggestions. Thanks for working on this, it's looking good from my perspective!

[Atemu]

Some small notes

[corngood]

I disagree, because the change happened after 24.11 was released, so it doesn't make sense to me to be in its release notes.

I thought about that, but it looks like release notes have been updated recently for older releases.

[corngood]

The only blocker for this really is combine-deps.nix, if that's changed to support JSON instead of nix files, we could already put it into practice.

Yeah, I'll try to do that at least for the next SDK updates.

[GGG-KILLER]

The only blocker for this really is combine-deps.nix, if that's changed to support JSON instead of nix files, we could already put it into practice.

Yeah, I'll try to do that at least for the next SDK updates.

Thanks, sorry I didn't do it myself but I really don't feel confident to even attempt it. I feel like I'd just end up breaking everything instead 😅

[corngood]

This all looks good. I added the backport label even though it's almost certainly going to fail the automatic backport. I'm sure some of the treewide changes will backport, but we'll have to do a pass on the rest.

[corngood]

Thanks for all the work on this. I'd like to merge it soon, but I just wanted to give anyone a last chance to raise an objection.

[Atemu]

The backport will probably have to be done manually.

We could also opt to not backport the tree-wide (as the Nix files still work) but that'd necessitate every update backport for dotnet packages to be backported manually.

Given that we have nearly perfect QA for this (eval is the same), I don't see a great risk.

[Atemu]

Given that every user involved in this thread reacted with a rocket, I think we're good to go ;)

[nixpkgs-ci]

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

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

git fetch origin release-24.11
git worktree add -d .worktree/backport-362278-to-release-24.11 origin/release-24.11
cd .worktree/backport-362278-to-release-24.11
git switch --create backport-362278-to-release-24.11
git cherry-pick -x 1726304559622bcd20c8e3b7006b41a09bada599 3cc4563eb2f435ddc0da0a4a39f509a7ff7ffb7c bccae9e7c0f234d41ae7c9aebbaaf4f65a27282c c94c5087cc19cc8339e2c4b3e7a1546f6e990fcc 8ea76507abb96c2bdb971b4f7fdadebeea627324 318b37a8d6d1991369606455b4b446a34811f49f 1cd9516969553291792021f1b327f0e2e2775b3c 2b4190a2c20a7d33062f5806b0a0f879082b2340