Would using thiserror crate be acceptable for the error handling?

[wt]

I would like to refactor the errors crate to use the thiserror crate. The patterns implemented in the module are very similar to the crate. The crate is widely used in rust libs. I think it would probably raise the quality of the code a bit to use the crate. Would this be an interesting change?

[Mingun]

If you want to use it just for defining error messages via derive macro then I think this is unnecessary. My points are:

• thiserror requires rust 1.56+, we require rust 1.52+. While I generally not against raising required version, that change also should give significant improvements
• overhead from manually implementing necessary traits are minimal
• new dependency increases build time. That is fine if it gives us new abilities but I prefer to avoid that if not

If you like also rework our errors to make them more ergonomic, then I'm not against. Actually, we should do that, some of our errors are cryptic. I also would like to have backtraces in our errors, but I'm unsure should we do something special to give them or we can get them automatically. Rust books is not clear about that.

The other thing that we lack in our errors is a position information (there is a dedicated issue for this -- #625). I would like to learn approaches used in other serde format libraries.

[wt]

This all sounds reasonable. I do think that thiserror is a good path forward. I think it might help with making the errors more ergonomic, which is part of my intent.