gridtracker2: 2.250914.1 -> 2.251106.7

[pyrox0]

The package builds fine without the in-tree lockfile, so there is no reason to have it. Also, having it breaks the ability to auto-update the package with the added update script. Therefore, best to remove it and not bloat the nixpkgs tree with unneeded lockfiles.

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[Cryolitia]

we may need it in some versions, although not all the versions, otherwise build would fail, explained in #446675 (comment)

[pyrox0]

The package-lock.json is not always necessarily updated when the package.json is modified. We would only have failing builds if the dependencies in package.json were updated but the package-lock.json was not, which from a brief glance through recent commits does not appear to be the case.

[Cryolitia]

LGTM