plasticity: fix build

[AmazinAxel]

Plasticity was not building after this commit. This change fixes the build by enabling dontCheckForBrokenSymlinks but this is a band-aid solution. Someone with more time and experience should go through to try fixing the symlinks, but this will fix the build in the meantime. The application works the same as before.

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.

[AmazinAxel]

I clicked the Sync Fork button on github and it added an additional commit - new to git so I don't know how to revert that
If this is a problem, let me know how to fix it - my apologies!

[Aleksanaa]

Someone with more time and experience should go through to try fixing the symlinks

So it doesn't have a report on failure? Or you can use tree -a ./result to check for links I guess

[AmazinAxel]

So it doesn't have a report on failure? Or you can use tree -a ./result to check for links I guess

It does have an error for each of the broken symlinks but I don't know what to do with that information. We could simply delete those symlinks but I don't know if that's the best course of action. For now to fix the build error, we can just skip the hook. If you think we should delete the symlinks instead I can make a new PR or update this PR
Relevant comment: #370750 (comment)

[FliegendeWurst]

LGTM