csplit print 0 on an error like gnu does

[HackingRepo]

fixes #13139

[codspeed-hq]

Merging this PR will degrade performance by 4.67%

❌ 1 regressed benchmark
✅ 326 untouched benchmarks
⏩ 46 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	sort_ascii_c_locale	16 ms	16.7 ms	-4.67%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing HackingRepo:patch-2 (ec8fb45) with main (b76d615)}

Footnotes

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

[sylvestre]

probably more something like:

  let res = if file_name == "-" {
      let stdin = io::stdin();
      csplit(&options, &patterns, stdin.lock()).map_err(Into::into)
  } else {
      File::open(file_name)
          .map_err_context(|| format!("cannot open {} for reading", file_name.quote()))
          .and_then(|file| csplit(&options, &patterns, BufReader::new(file)).map_err(Into::into))
  };

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/cut/bounded-memory (fails in this run but passes in the 'main' branch)
Note: The gnu test tests/csplit/csplit-heap is now being skipped but was previously passing.
Congrats! The gnu test tests/printf/printf-surprise is now passing!

[oech3]

GNU catches write error of stdout and ignore write error of stderr (with few expections).
Also lock() is not useful since write is done just once at here.

[HackingRepo]

so if that, that was a bit complicated, not all errors gnu print 0, that was the issue making it harder, what type of error it do that, we need known