errors: figure out if/how to expose ErrorKind

[cyphar]

ErrorKind is quite useful for our tests and most library users would probably want it for some uses, but it probably needs to have a better-designed way of distinguishing errors (ErrorKind::InvalidArgument vs ErrorKind::OsError(Some(libc::EINVAL)) is kind of unfortunate, for instance).

Kind of related to #60.