Move compile-fail tests that are rejected by the parser to parse-fail

[fhahn]

This PR moves all compile-fail tests that fail at the parsing stage to a parse-fail directory, in order to use the tests in the parse-fail directory to test if the new LALR parser rejects the same files as the Rust parser (as suggested by @brson in #21452). I also adjusted the testparser.py script to handle the tests in parse-fail differently.

However during working on this, I discovered, that Rust's parser sometimes fails during parsing, but does not return a nonzero return code, e.g. compiling /test/compile-fail/doc-before-semi.rs with -Z parse-only prints an error message, but returns status code 0. Compiling the same file without -Z parse-only, the same error message is displayed, but error code 101 returned. I'll look into that over the next week.

[rust-highfive]

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

[Potpourri]

You can also move here these two tests: use-mod-4.rs and use-ends-with-mod-sep.rs?

[nikomatsakis]

@bors r+ 4e544ca

nice

[nikomatsakis]

very excited to see this infrastructure coming together

[brson]

Nice.

[fhahn]

@Potpourri done. But there are some more files that fail during the parse stage. I'll try to fix the bug mentioned in the description as soon as possible.

[sanxiyn]

@bors r=nikomatsakis 01db9a4

[bors]

⌛ Testing commit 01db9a4 with merge 725cc06...

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-32-nopt-t, auto-win-32-opt, auto-win-64-nopt-t, auto-win-64-opt

[alexcrichton]

Unfortunately I think that this actually stopped running all these tests: #22118 (comment).

Don't sweat it too much, but I recommend doing extra tests on Makefile-based changes in the future, we unfortunately don't have automation in place to make sure tests are run!