Add underlying std::io::Error to IoError and add IpcError variant

[alexandreyc]

Which issue does this PR close?

Does not close any open issue.

Rationale for this change

I need to handle some kind of I/O errors (notably broken pipe errors) specifically and the current IoError variant does not permit it because it does not expose the underlying std::io::Error. Moreover, it looks to me that IoError is a bit misused, mostly in the IPC format and Flight crates. I introduced a new IpcError variant to have a better semantics of errors.

What changes are included in this PR?

• Add std::io::Error field to IoError variant
• Add IpcError variant to ArrowError
• Update conversion traits
• Replace usage of IoError within the IPC / Flights crates

I'm not 100% sure about the new semantics of every errors so feel to correct me.

Are there any user-facing changes?

Yes. Callers that handle IoError separately will need to update their patterns to include the new field and they will also need to handle the new IpcError variant.

[alexandreyc]

Just closed #4723 which was an earlier version of this.

[tustvold]

Makes sense to me, I think longer term we probably want to revisit the way that errors are handled. I do wonder if we would be better served using something like anyhow... #2725