Consolidate and Minimize Errors

[jasoncolburne]

Our errors are getting out of hand and we need to do something to reduce the number of variants. Many can be grouped and details specified at runtime. As an example, we could turn this:

    #[error("unexpected code error: {0}")]
    UnexpectedCode(String),
    #[error("unexpected count code error: {0}")]
    UnexpectedCountCode(String),
    #[error("unexpected op code error: {0}")]
    UnexpectedOpCode(String),

into

    #[error("unexpected code error: {0}")]
    UnexpectedCode(String),

And simply specify the op and count information in the supplied string.

[jasoncolburne]

We should note that this will make consuming code slightly harder to write, since the information becomes encoded rather than explictly cased.

[m00sey]

address err!(Error::NonZeroedLeadByte()) et al as well

[kentbull]

Meeting comment 03-30-23

We should clean this up before 1.0.0. It will take sitting down and designing an error set.

Usually in a library all the errors are wrapped to make a consistent interface. Do we want to do that or return the underlying errors from dependencies?

We will likely get to this when we are forced to by consuming it from other libraries.