Avoid using serde just for printing debug representations

[mhammond]

There were a lot of places where we derived Serialize just so a command-line tool could dump a JSON repr of a CI. Everything dumped also derives Debug, so now we just prefer using {:#?} and avoid using serde except where we actually need it (which is largely limited to parsing toml)

[bendk]

Seems good to me. As long as the output is human-readable it should be fine.

[mhammond]

clap-rs/clap#5088

[epage]

RE 5088

Clap is working as-expected.

Libraries should not be making policy decisions for their dependents by constraining upper bounds on version requirements. In fact doing so can be harmful to the entire ecosystem. We only do it for clap/clap_builder/clap_derive due to a special case related to proc macros. See https://doc.rust-lang.org/nightly/cargo/reference/specifying-dependencies.html#multiple-requirements for more details.

Instead, if you care about MSRV, you likely should be committing your lockfile. Note that Cargo has changed its guidance (blog post on this is upcoming). See the new guidance on the nightly docs: https://doc.rust-lang.org/nightly/cargo/faq.html#why-have-cargolock-in-version-control