regression: change in paths/CWD for rustdoc tests

[Mark-Simulacrum]

• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/better_embedded-0.4.0/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/code-path-0.3.2/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/gis_puller-0.1.1/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/haproxy-config-0.4.1/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/itf-0.2.4/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/minipng-0.1.1/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/stackdriver_logger-0.8.2/log.txt
• https://crater-reports.s3.amazonaws.com/beta-1.83-3/beta-2024-10-19/reg/text-to-png-0.2.0/log.txt

[ehuss]

This seems to have changed via #130582 (cc @notriddle). Reproduction:

src/lib.rs:

#![doc = include_str!("../README.md")]

README.md:

```rust
let x = include_bytes!("../examples/foo");
```

examples/foo: empty file

[apiraino]

Ok, removing the prioritization label as it is in T-rustdoc territory and it is being already nicely handled.

@rustbot label -I-prioritize

[MarijnS95]

Should this have regression-from-stable-to-stable Performance or correctness regression from one stable version to another. , given that this regression trickled into the 1.83 release (#133824)? Or is that not added retroactively for closed issues, even if other issues are closed as a duplicate of this closed issue?