Output tool's command in dryrun as well

I'd like to see what underlying command is shown even when using dryrun.
This is useful when testing addins or just checking their validity.
Right now one has to execute tasks to see the output (using Diagnostics verbosity) which might create issues, i.e. if one is testing "disk format" tool :)

No file or test is named. Start by tracing the dry-run handling and the existing Diagnostics-verbosity output path; done means the underlying command is shown during dry-run without executing the task or causing side effects.

Written by the indexing model from the issue text.