chore: update compile fail test stderr files

[RobWalt]

I noticed this while working on #18017 . Some of the stderr compile_fail tests were updated while I generated the output for the new tests I introduced in the mentioned PR.

I'm on rust 1.85.0

[alice-i-cecile]

Not sure why CI wasn't catching these...

[mockersf]

if CI didn't fail on that before, it means CI wasn't running them. Could you manage to get CI to fail before fixing them?

[RobWalt]

if CI didn't fail on that before, it means CI wasn't running them. Could you manage to get CI to fail before fixing them?

Nope doesn't seem like it was failing although it was clearly broken prior to b452c92

[Brezak]

if CI didn't fail on that before, it means CI wasn't running them. Could you manage to get CI to fail before fixing them?

We ignore differences between the stderr output of compile fail tests. When testing derive macros the backtrace would leak the location of the developers .cargo directory. I tried to filter the paths out but the filter would break randomly.

I seem to remember reading somewhere that rust now strips the path to .cargo in errors. I'll check tomorrow and if yes we can enable comparing the stderr output again.