Description

Currently, we mostly use RuntimeError or ValueError when pyodide-build cannot proceed. However, some of these errors are expected (e.g., invalid user input), which we can guide users to see the error message and handle it.

However, we currently have error tracebacks printed for most errors, which makes it difficult for users to determine whether the issue is their problem or a problem with pyodide-build.

So, I think it would be nice to

1. Categorize errors.
2. Do not show stack traceback for expected and actionable errors. Only print it for unactionable errors.