silverbullet: 0.9.4 -> 0.10.4

[costowell]

Bumped silverbullet, but tests are failing and not sure how to proceed.
First things first, this is a deno app. When I initially bumped the version and built, it was trying to download dependencies at runtime. I found out that the silverbullet.js that is provided on the release page is compiled with this behavior explicitly. Currently, this PR lets silverbullet create a temporary cache directory in /tmp, but this is less than ideal and also doesn't fix the tests. It'd be very challenging to build this in Nix, so I'm leaning towards making a couple issues on the original repo: 1) provide a deno.lock and 2) remove runtime evaluated dependencies.

Any feedback would be greatly appreciated.

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.

[phaer]

2.0.0 is in master now :)