chore(deps): update rust crate nix to 0.31.1 and libc to 0.2.180

[3v1n0]

We need those to complete #9432

Replaces #10433

[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)
Note: The gnu test tests/rm/rm-readdir-fail was skipped on 'main' but is now failing.

[sylvestre]

some jobs are failing

[3v1n0]

some jobs are failing

Yeah, it's unclear to me though, should we make all the dependencies to also be depending on the newer nix version? Or can we ignore the linting here?

[oech3]

Needed to wait codspeed and divan.

[oech3]

Or fix #9549 ?

[xtqqczze]

this PR has merge conflicts

[codspeed-hq]

Merging this PR will degrade performance by 3.02%

❌ 2 regressed benchmarks
✅ 286 untouched benchmarks
⏩ 38 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	du_max_depth_balanced_tree[(6, 4, 10)]	26.8 ms	27.7 ms	-3.01%
❌	Simulation	rm_recursive_tree	11.7 ms	12 ms	-3.02%

---

_{Comparing 3v1n0:bump-libc (3d3fadb) with main (bd58575)}

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. ↩

[github-actions]

GNU testsuite comparison:

GNU test failed: tests/date/date-locale-hour. tests/date/date-locale-hour is passing on 'main'. Maybe you have to rebase?
Congrats! The gnu test tests/misc/io-errors is no longer failing!
Congrats! The gnu test tests/tail/retry is no longer failing!
Note: The gnu test tests/pr/bounded-memory is now being skipped but was previously passing.
Note: The gnu test tests/rm/rm-readdir-fail was skipped on 'main' but is now failing.

[3v1n0]

We're now blocked on codspeed, I've subitted a PR, but should we care about a tool-dependency like this one?

[oech3]

Can you avoid this by using nix from outside of workspace crates?

[3v1n0]

Can you avoid this by using nix from outside of workspace crates?

Probably... Maybe we could just bump libc here and then bump nix for stty in #9432?

[xtqqczze]

I don't understand, we are already on libc 0.2.180 according to Cargo.lock?