terminal-notifier: fix relative path arguments

The wrapper's `--chdir` cd'd into the .app bundle before exec, so relative
path arguments (e.g. `-contentImage`) resolved against the bundle rather
than the user's working directory.

The chdir originally let the kernel find the bundle's `Info.plist` (and
thus the bundle identifier macOS notifications require) back when the
wrapper exec'd the binary by a relative path
(9d1748d384). makeWrapper now execs it by
its absolute path inside the bundle, so `Info.plist` is found regardless
of the working directory and the chdir is obsolete.

Assisted-by: Claude Code (Claude Opus 4.8)

pkgs/by-name/te/terminal-notifier/package.nix

@@ -47,8 +47,7 @@ stdenv.mkDerivation (finalAttrs: {
 
     makeWrapper \
       $out/Applications/terminal-notifier.app/Contents/MacOS/terminal-notifier \
-      $out/bin/terminal-notifier \
-      --chdir $out/Applications/terminal-notifier.app
+      $out/bin/terminal-notifier
 
     runHook postInstall
   '';