`cabal-validate` tracking issue

[9999years]

In #10320, I converted the Bash validate.sh script into a Haskell script, now known as cabal-validate.

To minimize discussion on that PR, I kept the implementation and CLI design unchanged.

However, I think that there's room for improvement in cabal-validate's behavior and CLI design. I'd like to get an idea of how people use cabal-validate so we can better serve their needs.

• cabal-validate: Steps are not granular enough, add groups of steps #10563
• cabal-validate: Too many ways to choose steps #10564
• cabal-validate: Steps change depending on options which choose steps #10565
• cabal-validate: Add --clean #10566
• cabal-validate: Build products are not shared with cabal build #10567
• cabal-validate: Skip "low-value" tests by default? #10568
• cabal-validate: Output is too verbose and not verbose enough #10569
• cabal-validate: Some steps shouldn't be steps #10570
• cabal-validate: Better time-summary #10571
• cabal-validate: "Keep going" mode #10572
• cabal-validate: if stdout isn't a tty, use GitHub Actions grouping #10595