Remove terse output requirement for parallel jobs

[Alexander-Aghili]

Requested feature: Remove terse output requirement for parallel jobs Use case: Full output while still having parallel capability

Currently, a terse output is required for running harnesses in parallel. Removing that barrier would allow for a full output while still allowing for parallel running of harnesses.

[jaisnan]

Hello, thanks for this suggestion. Would it be possible to link to a reproducer code that triggers an error when running harnesses in parallel without terse output?

[Alexander-Aghili]

cargo kani --workspace --exclude monitor -Z stubbing --jobs 4 --enable-unstable

error: Conflicting options: --jobs requires --output-format=terse