Improve MSRV failure CI JOB output display

[alamb]

Which issue does this PR close?

Closes #.

Rationale for this change

While debugging #6853 with @andygrove and @viirya , the CI output display for MSRV failures look 🤮 and doesn't tell you what the problem is

https://github.com/apache/arrow-rs/actions/runs/12207850027/job/34060002164?pr=6853

What changes are included in this PR?

It seems msrv has improved thier display since we list made this better

andrewlamb@Andrews-MacBook-Pro-2:~/Software/arrow-rs/arrow$ cargo msrv verify
  [Meta]   cargo-msrv 0.17.1

Compatibility Check #1: Rust 1.70.0
  [FAIL]   Is incompatible

  ╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
  │ error: package `clap v4.5.23` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.70.0 │
  │ Either upgrade to rustc 1.74 or newer, or use                                                                                             │
  │ cargo update -p [email protected] --precise ver                                                                                                 │
  │ where `ver` is the latest version of `clap` supporting rustc 1.70.0                                                                       │
  │                                                                                                                                           │
  ╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Are there any user-facing changes?

Example of new MSRV failure
XXX

[viirya]

cargo msrv verify
  shell: sh -e {0}
  env:
    RUSTFLAGS: -C debuginfo=1
    RUST_BACKTRACE: 1
Error: Process completed with exit code 1.

Looks like not working?

[alamb]

cargo msrv verify
  shell: sh -e {0}
  env:
    RUSTFLAGS: -C debuginfo=1
    RUST_BACKTRACE: 1
Error: Process completed with exit code 1.

Looks like not working?

Yeah, compared to the output with a tty this output is not good (probably why we dumped the logs).

I will maybe add a note / comment to the job instead saying that running cargo msrv locally will print out a nice error message

[alamb]

I have another idea I am trying out #6857

Will mark as ready for review if it looks reasonable