Make --test-show-details=direct the default

[ulysses4ever]

fix #7817, #8619

QA Notes

cabal test on a simple package with a test suite should give more verbose results than under the previously released cabals. Before, if there are no failures, you wouldn't see which tests have been run. Now you will. Bonus: if the package employs one of the testing frameworks (hspec, tasty, sidtest), you will enjoy colored output (unlike with previous cabal releases).

---

Please include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.
• Include manual QA notes if your PR relates to cabal-install.

Bonus points for added automated tests!

[Mikolaj]

At long last. Thanks for the docs.

[jneira]

does it no need automatic o manual tests? now it does not produce a log file by default it seems, and there is not broken test to update? 😢

not sure if it worths add the need test label tbh

[ulysses4ever]

@jneira indeed, I was going to but forgot to address automated testing in the PR message. As it stands, i don't believe it's possible to use the current test suite to test this change, and the only way is Manual QA.

I added a bit of notes for Manual QA but I could extend them, perhaps. I'm not very motivated to do that because I don't know if any manual QA will happen. I'd rather wait for a volunteer and see if they have particular questions. I'd be happy to answer.

Recently i saw many kinds of PRs that require extending the test suite in order to be tested, unfortunately (all in different manner, of course). I don't think it's fair to require that much of an effort for either of those contributions. Otherwise we will just stall.

[ulysses4ever]

I'm fine with applying any labels that people think would be helpful, of course. I'm not sure what that should be.