Spec and prototype omitting the traceback for known user errors

### What needs to get done

Design a mechanism to avoid outputting the craft-tool traceback (to the log file and terminal) in case the error happens for a cause that we know for sure isn't a bug (e.g. a plugin build failure).

### Why it needs to get done

The current log is super noisy and makes it hard to find the "true" cause of a failure:

The issue names no file, test, or entry point. Start by locating where craft-tool tracebacks are emitted to the log file and terminal, then examine how known user errors such as plugin build failures are represented. Done means a documented design and prototype that suppresses those tracebacks without hiding the underlying failure cause.

Written by the indexing model from the issue text.