Permit running sqllogictest as a rust test in IDEs (+ use clap for sqllogicttest parsing, accept (and ignore) rust test harness arguments)

[alamb]

Which issue does this PR close?

Closes #8287
Closes #4769

Rationale for this change

Basically I want to be able to run sqllogictest in RustRover more conveniently (and also make it easier for @tustvold to work in DataFusion so he does it more ;) )

In the UI I enter this:

However, what the IDE actually runs is this (notice the new arguments)

What changes are included in this PR?

1. Rewrite the sqllogictest CLI parsing command to use clap Use Clap for sqllogictest #4769
2. Add support for the CLI options that RustRover seems to slap on to its invocation, and warn if they are used to avoid confusion

Are these changes tested?

Yes, by existing CI tests

I also tested manually and I can now run these tests just fine in RustRover/ Here is what a session looks like:

/Users/andrewlamb/.cargo/bin/cargo test --color=always --test sqllogictests --no-fail-fast -- --format=json -Z unstable-options --show-output
Testing started at 8:22 AM ...
    Finished test [unoptimized + debuginfo] target(s) in 0.12s
     Running bin/sqllogictests.rs (target/debug/deps/sqllogictests-170b3f54eec6b11f)
WARNING: Ignoring `--format` compatibility option
WARNING: Ignoring `-Z` compatibility option
WARNING: Ignoring `--show-output` compatibility option
Running "binary.slt"
Running "options.slt"
Running "cte.slt"
Running "ddl.slt"
Running "wildcard.slt"
Running "arrow_files.slt"
...

Are there any user-facing changes?

No, it is entirely developer facing

[alamb]

FYI @xudong963 (as you originally filed #4769) and @tustvold (as you originally mentioned #8287)

[tustvold]

I worry this might be fragile if IDEs choose to enable other options. I'm curious why you decided against making an explicit binary and then a test target that just calls the binary entrypoint but with no arguments, as was described in the initial ticket?

[alamb]

I worry this might be fragile if IDEs choose to enable other options.

I agree it is fragile (but easy to fix)

I'm curious why you decided against making an explicit binary and then a test target that just calls the binary entrypoint but with no arguments, as was described in the initial ticket?

I tried this approach but then decided on this one because (at least for me in RustRover) I felt it would be easier to use / understand.

making a different binary ended up being something like cargo run -p datafusion-sqllogictest --bin sqllogictest or cargo run -p datafusion-sqllogictest --bin runner (though maybe my Cargo.toml fu is not as good as it could be)

And then when I started trying to add some documents on how to run this command, it got confusing quickly

Thus I figured it would be easier to understand if it just looked like the test binary.

[alamb]

I added some additional warnings in 9506116 to reduce confusion