Spec and prototype omitting the traceback for known user errors

[tigarmo]

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:

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3655.

This message was autogenerated