Display errored command output

[jknaudt21]

Describe the bug

When running a ! terminal command, if the command fails, the cli swallows the error and there's no way of seeing the output.

This makes it difficult to diagnose what is going on within the session.

Affected version

0.0.382 Commit: 18bf0ae

Steps to reproduce the behavior

1. Open copilot
2. Type an invalid ! command - e.g (!adofkj)
3. Observe that there's no visibility why the command failed - would expect to see the text "'adofkj' is not recognized as an internal or externa command"

Expected behavior

The output of the command is shown and there's clear insight on what ran.

Additional context

• Windows Terminal
• Windows x86

[RyanHecht]

This has bugged me for a while now. Your issue inspired me to draft a PR to fix it -- it's in the queue to be reviewed now!

[RyanHecht]

This will be out in tomorrow's prerelease!