Flycheck error message not logged

[Noratrieb]

In everyone's favourite workspace, I made bootstrap sad, causing the flycheck invocation to fail (unrelated to r-a).
I noticed this because r-a wasn't giving suggestion and the big warning sign was shown. Indeed, the logs confirmed this:

2024-03-28T19:01:16.007328Z ERROR flycheck: Flycheck failed to run the following command: CommandHandle { program: "python3", arguments: ["x.py", "check", "--json-output", "--build-dir", "build-rust-analyzer"], current_dir: Some("/home/nils/projects/rust2") }
2024-03-28T19:01:18.554495Z ERROR flycheck: Flycheck failed to run the following command: CommandHandle { program: "python3", arguments: ["x.py", "check", "--json-output", "--build-dir", "build-rust-analyzer"], current_dir: Some("/home/nils/projects/rust2") }
2024-03-28T19:01:20.449995Z ERROR flycheck: Flycheck failed to run the following command: CommandHandle { program: "python3", arguments: ["x.py", "check", "--json-output", "--build-dir", "build-rust-analyzer"], current_dir: Some("/home/nils/projects/rust2") }

Sadly, by default it does not show the standard output of the flycheck command, making it annoying try to figure out what happened (I had to copy the command and clean it up manually to figure out what went wrong (and then fix it).
If r-a just logged standard error of the command, it would have been easier to see what's wrong.

Bonus: if r-a used <std::process::Command as Debug>, it would actually show a very pretty copy-able command invocation :)