yazi-unwrapped: build new yazi-cli tool

[eljamm]

Description of changes

See sxyazi/yazi#914

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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

[eljamm]

Result of nixpkgs-review pr 321937 run on x86_64-linux 1

2 packages built:

• yazi
• yazi-unwrapped

[eljamm]

Tested the tool a little bit following the yazi DDS docs page and it seems to work.

Testing steps

• Open yazi and enter a subshell
• Find out the instance ID using echo $YAZI_ID. You can exit the yazi subshell, now.
• In another shell, invoke a command to the instance using the cli. For example, to change the directory:

./result/bin/ya pub "1719138555289021" dds-cd --str "/tmp"

• Back in the yazi instance, you'll notice that the working directory has changed

[XYenon]

Yazi the wrapper also need to be changed to make ya available.

[XYenon]

I have added it to default-members, so we can remove this next version.

https://github.com/sxyazi/yazi/pull/944/files

[eljamm]

So do you think we should just wait for the next release or do we add a message like this:

  # remove in the next release
  cargoBuildFlags = ["-p" "yazi-fm" "-p" "yazi-cli"];

[eljamm]

Yazi the wrapper also need to be changed to make ya available.

Since the wrapper changed in 321076, I didn't want to modify it here until it was merged to avoid conflicts.

Would it have been better if I opened this as a draft, perhaps?

[eljamm]

The wrapper PR was merged so I've added the cli tool to the wrapper, tested again, and everything appears to be working.

I've also added a note to remove the cargo flags in the next release.