grafema-haskell-binary-stale-priority

Fix stale Haskell analyzer binaries silently being used by the orchestrator even after a successful rebuild. Use when: (1) modified packages/js-analyzer/ or other Haskell analyzer source, ran scripts/build-native.sh ... cabal install, but a subsequent grafema analyze shows old behavior (missing new edges, no new node types, etc.), (2) ~/.cabal/bin/grafema-analyzer has fresh timestamp but grafema analyze produces output as if the change didn't happen, (3) a test verifying new analyzer output passes locally in unit tests but fails in end-to-end runs that go through the orchestrator. Root cause: the Rust orchestrator's resolve_binary checks ~/.grafema/bin/<name> BEFORE ~/.cabal/bin/<name>, so any stale copy that was once installed there (possibly months ago) shadows the fresh cabal install output.