Make errors more structured

[fubuloubu]

Describe

Downstream integrators want better support for displaying errors from this service, create a more structured way for displaying compiler errors so that they can be displayed

Specification

Remix's error structure is as follows:

interface CompilerError {
    status: string = "failed"; // NOTE: We don't really need to specify this as anything else
    message: string; // Use `e.message`
    column: number;
    line: number;
    errorType: string; // Use `e.__class__.__name__`
}

Not all errors would it make sense to change, but the result obtained from the /errors/{task_id} endpoint should be described this way, for any configuration or compile-time exceptions

Dependencies

n/a

[joeizang]

errorType can be SyntaxError Exception, which I think was a type of error I saw when testing.

[fubuloubu]

errorType can be SyntaxError Exception, which I think was a type of error I saw when testing.

right, but from your perspective it's just a string that gets printed right?