Allow progress console_output_style even when capture=no

[reaperhulk]

What's the problem this feature will solve?

When running large test suites like pyca/cryptography we see significant (up to 40%!) slowdown on some jobs when capturing is enabled. However, enabling capture disables "progress" , which in turn results in extraordinarily long lines on GitHub Actions, which breaks browsers' ability to load CI output.

Describe the solution you'd like

In #3038 the "progress" output was disabled when capture=no (defaulting back to classic) because any extraneous stdout/stderr from the tests will mess up the output. However, for users who are willing to risk accidentally leaving code that might write to stdout/stderr it would be great to support a flag that would re-enable progress info.

Alternative Solutions

• Capturing could possibly be made (much) faster, thus negating the desire to disable it to gain performance.
• A new output style could exist which limits line lengths but does not attempt to do "progress" style fancy output.