Build: verbose error in default errors

[agjohnson]

Noticed this during deploy today:

The error message is a lot and probably isn't more helpful than the code formatted section below. We should decide what to do in cases like these, and perhaps the answer is that if we can't give a clear error message, we show a generic error. Alternatively, we should at least be code formatting the error string in these cases, but I'm not sure that is more helpful than just the build output.

Long term, I'd like a helpful, clear message that links to the failed command for more context. This is probably a generic message in a lot of cases. But, for this case for example, we could give the user guidance like "There was an issue while installing your Python dependencies. Make sure you have the correct URLs and permissions".

[agjohnson]

Actually, i guess I'd call this one a bit more of a bug after seeing a few examples here.

[humitos]

This was solved already and we have other issues to track the long-term idea.