parse errors are hard to troubleshoot

[rbtcollins]

A typical parsing error might look like this:

    Finished dev [unoptimized + debuginfo] target(s) in 3.15s
     Running `target\debug\examples\client.exe`
Error: Unable to parse response body: missing field `matchExpressions` at line 1 column 6685
 Caused by missing field `matchExpressions` at line 1 column 6685

error: process didn't exit successfully: `target\debug\examples\client.exe` (exit code: 1)

There's not enough of the original context preserved to tell whats going on - and as API contents are usually one-off, its likely that no offline fix is possible (imagine this throws during a functional test suite).

It would be good, for instance, to provide the current parse context (e.g. is it a NodeMatch) or even a tree, or the input bytes, or some combination.

[anguslees]

We're limited by what serde gives us here (or rather: improvements are best done as improvements to serde). It think the best we can do within kubernetes-rs is to keep the original text as part of this error object, so "line 1 column 6685" can be more easily interpreted.

Error handling generally needs to be improved ("needs to be implemented" would be more correct).