Improve error messages

[lenguyenthanh]

Error messages should tell where and why error happen

[nvduc91]

I saw we using NoStackTrace therefor no stacktrace provided?
And we could define some rules to present errors. Could be some point like:

• Should we provide stacktrace? if yes, full of it or parts of it?
• rules to presenting the errors if needed (custom before show up/make it shorter ...)
• impl and add tests for it.

[lenguyenthanh]

* Should we provide stacktrace? if yes, full of it or parts of it?

We use Error as data so we don't need stacktrace.

* rules to presenting the errors if needed (custom before show up/make it shorter ...)

Error Messages should be able to tell where (e.g. line 8 column 9) and why (e.g. "Operands must be numbers.").

So we'll need a new data structure to present data. Probably something like this:

case class ErrorMessage(
  val location: Span,
  val message: String)
)

Our problem is ParserError doesn't have location on it, so we have to fix that first.

For inspiration Rust diagnostic code: https://github.com/rust-lang/rust/blob/4e82f35492ea5c78e19609bf4468f0a686d9a756/compiler/rustc_errors/src/json.rs#L185