Improve error definitions

[Enet4]

Although error types are already statically delimited, errors emerging from the library currently contain little to no context about where they happened. This is an example of an error value which may emerge when opening a file: DataSetSyntax(PrematureEnd)

Requesting a backtrace is not useful because the error was raised with the ? operator, without keeping the full backtrace from the origin of the error at the library level. quick-error has been originally employed as a means to easily create error types, but for a solution of this scale, it becomes harder to work with and does not contribute to good errors.

As declared in the roadmap, it is of my interest to change the existing error definitions to something more informative and organized. I will try to rewrite existing errors with the use of another crate (likely either snafu or thiserror), which will provide the much needed quality of these error values.