tsort: Use rustc-hash

[oech3]

3% perf gain?
Since Fnv is already used at ls (assuming ls is not used for unreliable files) , no reason to avoid non-crypto hash func.

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/tail/inotify-dir-recreate (fails in this run but passes in the 'main' branch)

[codspeed-hq]

CodSpeed Performance Report

Merging this PR will improve performance by 16.74%

_{Comparing oech3:ts3 (cd2a8e2) with main (b311460)}

Summary

⚡ 4 improved benchmarks
✅ 280 untouched benchmarks
⏩ 38 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	tsort_complex_dag[50000]	85.4 ms	73.1 ms	+16.74%
⚡	Simulation	tsort_tree_dag[(10, 3)]	34.2 ms	29.4 ms	+16.15%
⚡	Simulation	tsort_linear_chain[1000000]	1.6 s	1.4 s	+10.48%
⚡	Simulation	tsort_wide_dag[100000]	130 ms	116.5 ms	+11.61%

Footnotes

1. 38 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[xtqqczze]

@oech3 Have you tried foldhash yet?

[oech3]

No. But I saw xxhash3 was bad.

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/shuf/shuf-reservoir (fails in this run but passes in the 'main' branch)
Skip an intermittent issue tests/sort/sort-stale-thread-mem (fails in this run but passes in the 'main' branch)